Frequently asked

Honest answers about how we work.

Everything we get asked on a first call — scope, pricing, timelines, the parts that usually go wrong. If something is missing, ask us directly.

How we work

How do we trust the timeline?

Every engagement starts with a fixed scope and a milestone map — no vague sprints, no scope creep. We publish a kickoff brief before any work begins, and you review every milestone before we proceed. If a milestone slips, we tell you within 24 hours and update the map.

What's a typical engagement length?

Most Full Build engagements run 8–16 weeks from kickoff to live. Embed engagements run in 4-week cycles with explicit renewal points. Teardowns are 48 hours, free, and don’t require a call.

How do milestones work?

We break the scope into 3–6 milestones with explicit acceptance criteria. You review and sign off on each one before we move on. If a milestone fails review, we revise on our time.

Pricing & engagement models

How do you price work?

We price the engagement, not the hour. Every scope gets a fixed price tied to milestones, so you know what you’re paying before any work begins. No hourly billing, no time-and-materials surprises.

What's the minimum engagement size?

Full Build engagements typically start at the size of a 6-week MVP scope. Embed engagements start at a single 4-week cycle. Teardowns are always free.

Do you take equity?

Occasionally, for the right early-stage team and the right structure. It’s never a substitute for cash — we want skin in your game, not a discount on ours.

Compliance & security

Do you handle SOC 2 / HIPAA / ISO 27001?

Yes — and we run it in parallel with the build. By the time your product is code-complete, your evidence package and policy set are already drafted and ready for audit prep.

Will I own the code and IP?

Yes. All source code, infrastructure, design files, and documentation are yours from day one. We deliver into your repos, your cloud accounts, and your tools — not ours.

Tooling & process

How is this different from Cursor or GitHub Copilot?

Cursor and Copilot are engineering productivity tools that make individual developers faster. We're a delivery team that owns the whole product surface — product strategy, design, engineering, compliance, and go-to-market. We use AI tools throughout, but the output is a shipped product, not faster code.

We're early-stage. Is this for us?

Possibly. We work best with teams that have a clear problem, a target user, and a 90–180 day runway to ship something real. If you're pre-idea, we’re probably too early. If you're post-idea and need to ship fast without building a 15-person team, that’s exactly what we do.

Didn't find your answer?

Send us the question directly — we read every message and reply within one business day.

Ask us anything →

Let's build your product. In parallel.

Send your roadmap. We'll send back a free 1-page teardown. No call required.

Book a 30-min intro call →