Can Pitch be vibe coded?
Build structured presentations with reusable blocks, comments, and polished export
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Pitch, build structured presentations with reusable blocks, comments, and polished export. The hard boundary is real-time collaboration, templates, analytics, and team content management, plus editor polish, assets, collaboration, and distribution.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
medium editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Build structured presentations from reusable blocks on a canvas, edit text and media, support comments, and export a finished deck as SVG or PDF.
- Generate a constrained editing workflow with reusable templates and deterministic exports.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- real-time collaboration, templates, analytics, and team content management
- huge template and asset libraries
- real-time multiplayer
- brand governance
- Permissions, presence, and shared workflows are difficult to simplify.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
Why people still pay
People still pay for Pitch because people pay for a vast ready-made design system and a collaboration surface that behaves predictably under deadline. The recurring cost buys canvas correctness, fonts, exports, templates, asset rights, multiplayer state, and accessibility, not just the visible interface.
Permissions, presence, and shared workflows are difficult to simplify.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Pitch
Context
**Pitch** — Build structured presentations with reusable blocks, comments, and polished export. It currently costs $20/mo.
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Pitch, build structured presentations with reusable blocks, comments, and polished export. The hard boundary is real-time collaboration, templates, analytics, and team content management, plus editor polish, assets, collaboration, and distribution.
This brief describes a focused, single-operator replacement for the part of Pitch that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Build structured presentations from reusable blocks on a canvas, edit text and media, support comments, and export a finished deck as SVG or PDF.
Generate a constrained editing workflow with reusable templates and deterministic exports.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Modern desktop browser.
Local fonts and images.
Data and integrations
Optional image-generation API key.
Each of these needs a real account, credential, or quota. Set them up before writing feature code.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build a personal replacement for Pitch in an empty repository.
Use Next.js 15, TypeScript, React, Tailwind CSS, IndexedDB, and SVG; do not offer alternative stacks.
The core loop is: build structured presentations from reusable blocks on a canvas, edit text and media, support comments, and export a finished deck as SVG or PDF.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Create a fixed-size SVG canvas with zoom, pan, selection, alignment, and snapping.
Support text, rectangles, circles, images, groups, layers, and reusable components.
Add a small set of high-quality starter layouts relevant to the product category.
Implement undo, redo, autosave, and import or export of a portable project JSON file.
Export SVG and print-ready PDF without rasterizing text unnecessarily.
Keep all assets local and display missing-font warnings before export.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out real-time multiplayer editing.
Deliberately leave out a commercial stock-asset library.
Deliberately leave out enterprise brand controls and approval workflows.
Finish by running the tests and listing the exact commands used.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
Real-time collaboration, templates, analytics, and team content management.
Huge template and asset libraries.
Real-time multiplayer.
Brand governance.
Permissions, presence, and shared workflows are difficult to simplify.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
What you still own after launch
Secure credentials, rotate secrets, and handle provider rate limits.
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Risk
**Manageable.** A personal version is realistic if you test the critical journey and keep reliable backups.
Editorial confidence in this assessment: medium. No independent one-shot implementation is linked yet.
Prior art
Working open-source software you can read, fork, or borrow from before starting:
[Penpot](https://github.com/penpot/penpot) — Mature open-source collaborative design platform with SVG-native editing
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/pitch
You still own the product
- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
Open-source prior art
Before you start
Can Pitch be vibe coded?
Partly, if you narrow it. The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Pitch, build structured presentations with reusable blocks, comments, and polished export. The hard boundary is real-time collaboration, templates, analytics, and team content management, plus editor polish, assets, collaboration, and distribution.
What can an AI coding agent reproduce from Pitch?
Build structured presentations from reusable blocks on a canvas, edit text and media, support comments, and export a finished deck as SVG or PDF. Generate a constrained editing workflow with reusable templates and deterministic exports. A responsive interface with real empty, loading, success, and error states.
What will a DIY Pitch replacement still be missing?
real-time collaboration, templates, analytics, and team content management; huge template and asset libraries; real-time multiplayer; brand governance; Permissions, presence, and shared workflows are difficult to simplify.; The last 20 percent is sync, migration fidelity, speed, and edge cases.
What do I still own after building a Pitch alternative?
Secure credentials, rotate secrets, and handle provider rate limits. Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss.