FAQ
/ Common questions

Questions,
answered
honestly.

The things people ask us most often. If yours isn't here, just ask — we read every inquiry personally.


01

About working together.

How does an engagement typically start?

A short conversation. Thirty minutes is usually enough to understand the shape of the problem, what you’ve already tried, and whether we’re a good fit. If we are, we’ll propose a clarify phase: a one-to-two week discovery that produces a clear recommendation for the work ahead — with us, or on your own.

What sizes of project do you take on?

From a focused two-week advisory engagement to multi-quarter platform builds. Most projects sit in the four-to-sixteen-week range. If you’re a founder with a six-week window before fundraising, that’s a shape we know well. If you’re a CTO contemplating a multi-year platform migration, that’s a shape we know too.

Do you do fixed-bid work?

Yes — for projects with well-defined outcomes. After the clarify phase, we’ll usually be able to fixed-bid the next stage. For genuinely exploratory work, we prefer time-and-materials with a clear weekly cap so neither side is over-committed.

Who actually does the work?

Senior practitioners, throughout. The person you meet in the kickoff is the person making architectural calls in week twelve. We assemble small, senior teams — not pyramids that depend on layered handoffs.


02

About the work itself.

Do you build with our existing team, or replace it?

Both, depending on what you need. We embed alongside in-house teams to add senior capability, lead a defined workstream while you grow, or take full ownership of a build until handoff. We always design the engagement so your team is stronger at the end than at the beginning.

What’s your technology stack?

We choose the stack that fits the problem, not the other way around. In practice that often means TypeScript across web and mobile (React, Next.js, React Native), cloud-native infrastructure (AWS, GCP, Cloudflare), and the modern LLM tooling ecosystem for AI work. We’re stack-agnostic about your existing systems — whatever’s there, we’ll meet it.

How do you handle AI honestly?

We use AI where it earns its place. That means starting from the workflow, not the model; setting up evaluation before production; keeping humans in the loop wherever stakes, regulation, or trust require it; and being upfront about cost, latency, and failure modes. We won’t recommend AI for a problem that doesn’t need it.

What happens to the code and IP when we’re done?

You own everything we produce. Code, designs, documentation, decision records — all transferred on completion. We design for a clean handoff from day one, so there’s no scramble at the end and no part of the system only one person can reason about.


03

About the practical bits.

Where are you based, and how do you work?

We’re a US-based, remote-first practice with experience delivering across global time zones. We travel when the work calls for it — especially for kickoff workshops and field research — and otherwise operate as a tightly integrated remote team.

What does an engagement cost?

It depends on the shape and scope of the work — a focused advisory phase is a fraction of a full platform build. We price each stage explicitly: a short clarify phase first, then a fixed bid (or capped time-and-materials) for the build once we both understand what’s actually needed. We’re transparent about cost early and won’t put a number on the work before we’ve done enough to understand the problem.

Do you sign NDAs?

Routinely. For the initial conversation we’d usually skip it; once we’re working with you, mutual NDA is standard and we have a clean template ready to send. We treat every engagement as confidential by default.

What if it’s not a fit?

We’ll tell you, candidly, and where we can we’ll point you to a better fit. A bad engagement helps no one. We’d rather pass on work we can’t do well than take it on and disappoint.


Still thinking?

Just ask.

A short message is enough to start a useful conversation. We read everything and reply within two business days.