Questions, answered.
Everything founders and product leaders ask us in the first call. If yours isn't here, ping us — we'll add it.
What does a typical project look like?+
Most engagements start with a 2-week discovery sprint, followed by a 8–16 week build. We work in weekly cycles with live demos and async reviews so leadership always sees progress.
Can you work with our in-house team?+
Yes — the majority of our engagements are embedded pods. We plug into your Linear/Jira, Slack, GitHub and Figma and follow your engineering standards.
What's the minimum engagement size?+
A focused sprint (2 weeks, ~$8.5k) is the smallest way to work with us. For build partnerships we ask for a 3-month minimum to make the roadmap meaningful.
Which stack do you build on?+
TypeScript everywhere. React with TanStack Router/Query on the frontend, Postgres + Supabase or Node/Edge on the backend, Tailwind for styling. We're pragmatic — we use what best fits the problem.
Do you handle DevOps and deployments?+
Yes. We ship to Vercel, Cloudflare, AWS or your existing infra with CI/CD, previews, logging and error tracking configured from day one.
How do you handle QA?+
Every project gets automated test coverage on critical paths, Playwright end-to-end flows, and a manual pre-release checklist.
Who owns the code and design?+
You do. All work product is transferred to your entity on payment. We keep the right to reference the work in our portfolio unless you request confidentiality.
How do you handle NDAs?+
We're happy to sign yours, or use our mutual NDA — usually completed within 24 hours.
How do you handle data and security?+
We follow least-privilege access, use SSO with 2FA on every tool, encrypt data at rest and in transit, and can accommodate SOC 2 / HIPAA / GDPR-aware engagements.