Questions
Hard answers to soft questions.
We build for founders and executives who don't have time for spin. The truth about timelines, code ownership, and how we actually ship.
01 — Working together
How an engagement actually runs.
Process, communication, and what week one looks like.
How quickly can we start?+
Typically within 1–2 weeks. We scope discovery and align on a start date on our first call — and once we start, your first demo is on screen by day 7, with a shippable slice by day 14.
Do you work with startups or enterprise?+
Both. We tailor process and team composition — the craft standard doesn't change. Since 2014 we've shipped for two-person founding teams and for public companies.
How do you handle communication?+
Shared boards, a weekly demo every week, and a direct line to the senior team building your product. No account-manager relay, no status theater.
Who will actually work on my project?+
Senior designers and engineers only — one remote-first team, and nobody on your build is learning on your dime. The people on the kickoff call are the people who ship.
Can you sign an NDA?+
Absolutely. We're happy to sign your NDA before discovery — send it with your brief and it comes back signed with the first reply.
02 — Pricing & scope
What it costs and why.
Models, floors, and how scope changes are handled.
What's your pricing model?+
Fixed-scope projects, monthly retainers, and dedicated pods. We recommend the fit after discovery — and whichever model you pick, the number is in writing before work starts.
Why do you publish "from" prices?+
Because scope is the price. The published floor is real — nobody has ever paid less, and after one scoping call you get an exact figure that doesn't move unless the scope does.
What happens if scope changes mid-project?+
We quote the delta before building it, you approve in writing, and the timeline adjusts with it. That discipline is why we've issued $0 in surprise change orders since 2014.
Can I pause a retainer?+
Yes — Care plans are month-to-month. Pause or cancel with 30 days' notice, no penalty, and your rate is locked when you return.
What tech stacks do you use?+
TypeScript, React, Node, Go, Postgres, and cloud-native infrastructure on AWS/GCP. Boring where it should be boring, sharp where it earns its keep.
03 — After launch
What happens when it ships.
Ownership, handover, and the months after go-live.
Who owns the code and IP?+
You do. Full transfer on delivery, with clean docs and repository handover. No licensing games, no hostage code.
Do you offer post-launch support?+
Yes — 84% of clients continue on a Care plan for maintenance, iteration, and growth. It's month-to-month precisely so that staying is a choice, not a lock-in.
Will my site stay fast after handover?+
We deliver at a 98 median Lighthouse score and document how to keep it there. On a Care plan we monitor performance monthly and fix regressions before you notice them.
What if I want to take it in-house later?+
That's the plan working. Docs and handover are part of every engagement, and we'll onboard your hires on real calls — 98% client retention comes from being easy to leave, not hard to.
Still have questions?
Ask a person, not a page.
Send the question that isn't answered here. A senior replies within one business day — usually with more detail than you asked for.