/process
How a project actually runs.
Six phases from the first message to post-launch support. Honest timelines. Real deliverables. No agency theater.
The phases
Discovery
1–2 daysA short conversation — async message or a 30-minute call — to understand what you're building, why, and for whom. No intake form to fill out, no agency theater. Just enough context to know if it's a good fit and what it will take.
- Clear problem statement
- Rough scope and constraints identified
- Fit assessment (is this the right engagement?)
Scope & Estimate
1–3 daysA written scope document: what will be built, what won't, and why. Includes a timeline and fixed price or capped range. No vague "it depends" — you get a number you can actually plan around. Scope changes require a conversation, not a surprise invoice.
- Written scope document
- Fixed price or capped estimate
- Timeline with key milestones
- What's explicitly out of scope
Design & Architecture
2–5 daysFor web apps, this means defining the data model, auth flows, and key screens before writing a line of product code. Design decisions made here are far cheaper than ones made during build. You review and approve before code starts.
- Database schema design
- User flow diagrams for key interactions
- Component and layout sketches
- Tech stack confirmation
Build
1–6 weeksThe main construction phase. Code is pushed to a feature branch on a private repo and deployed to a Vercel preview URL from day one — you can watch it take shape in real time. No black-box development, no "we'll show you at the end." Weekly check-ins keep scope from drifting.
- Working preview deployment from day 1
- Weekly progress check-ins
- All core features implemented and tested
- Admin panel, auth, payments (as scoped)
Launch
1–2 daysProduction deployment, custom domain, SSL, environment variables, and a final round of cross-device testing. For SaaS products, this includes confirming payment flows and email deliverability are healthy. You go live with confidence, not fingers crossed.
- Production deployment to custom domain
- SSL, DNS, and redirect configuration
- Payment and email flow verification
- Cross-device and browser testing
Support & Iteration
OngoingMost projects benefit from a maintenance retainer after launch — dependency updates, bug fixes, and small feature additions. Monthly retainers are flexible: pause when you don't need anything, restart when you do. Larger feature additions are scoped and priced like a new project.
- Monthly dependency updates
- Bug fixes with same-day turnaround
- Small feature additions (< 4 hrs)
- Monthly summary of changes made
Working principles
One point of contact
You work directly with Cedar — not an account manager relaying messages to a developer you'll never speak with.
Transparent pricing
Fixed prices or capped ranges. No change orders for scope you already agreed to. No surprise invoices.
Visible progress
Preview deployments from day one. Every change is live on a URL you can bookmark and share.
Real stack, real code
Next.js, TypeScript, Postgres — not Webflow, no-code tools, or proprietary platforms that lock you in.
Common questions
Do I need to know exactly what I want before reaching out?
No. A rough idea and a goal is enough. The discovery phase exists to sharpen that into a clear scope. You don't need a spec document — just a problem worth solving.
How involved do I need to be during the build?
Weekly check-ins (15–20 minutes) and review of the preview URL a few times. You're not managing the project — you're making decisions when they need to be made. Low overhead by design.
What if my requirements change mid-build?
Minor pivots are normal and usually absorbed. Significant scope changes get a quick re-scope conversation — new features are priced and added to the timeline transparently. Nothing added silently to an invoice.
Do I own the code?
Yes. You own everything — code, database, domain, deployments. The repo is transferred to you on final payment. No vendor lock-in, no recurring license fees for software I wrote.
Ready to start?
Kick off with discovery — a short conversation about what you're building. No commitment required.