Question 1

Who owns the IP if agents are writing the code?

Accepted Answer

You do — work-for-hire, day one. Every commit lives in your repo, every deploy runs on your account, and every PR is mergeable by you with a single click. We don’t hold a proprietary model or a private training corpus built on your work, and nothing we ship retains our claim once the engagement ends. The agents are the workforce; the artefacts, the repo, the domain, and the IP are all yours.

Question 2

How are change requests handled mid-sprint?

Accepted Answer

They get appended, not re-invoiced. When the scope shifts, we add a line to the same engagement — a revised acceptance-criteria bullet, a single PR carrying the diff, and a one-paragraph note in the daily stand-up so you can see what changed and why. Response SLAs sit at four business hours for PR review notes on Growth and one business day for incident triage on the same tier, so a mid-sprint pivot never stalls on a calendar invite.

Question 3

How is this different from Fiverr or Upwork?

Accepted Answer

Four axes. First, you’re buying a subscription or a fixed-fee milestone, not hours on a clock — the engagement is priced on outcomes, not bids. Second, you’re getting a coordinated swarm of specialist agents behind one accountable lead, not a marketplace of freelancers you have to vet yourself; the old studio model of weekly status chasing, hourly retainers billed in 15-minute increments, and stand-up threads that go quiet on a Friday afternoon is exactly what we replaced. Third, work starts this week, after a written scope and a sign-off — no proposal round, no portfolio review. Fourth, the surface is the same throughout: your repo, your inbox, your branch policy. We don’t host a parallel dashboard you have to remember to log into.

Question 4

How fast can a project start?

Accepted Answer

Send a brief through the intake form and a written scope lands in your inbox within 72 hours — the SLA is the same on every tier. Once you’ve signed off on the scope, work starts the next business day. There’s no proposal cycle, no interview loop, and no calendar Tetris before the first PR. If 72 hours feels too slow for the question you have, the email fallback goes to the same inbox and the founder reads it personally.

Question 5

What’s the tech stack?

Accepted Answer

The site you’re reading is the answer — Next.js 16, React 19, Prisma, and Postgres, all running on the deploy platform that handles the infra behind the scenes. Agents work inside your repo using whatever stack you already have: TypeScript, Python, Node, Go, whichever fits the surface. We don’t drop a new framework into your tree to justify our own tooling, and there’s no proxy or vendor lock-in to swap out later — the deploy target is your account, the code is your code, and the rest is configuration you can read.

Question 6

How do I see progress without chasing?

Accepted Answer

The reporting cadence is set by the tier, not by you remembering to ask. Starter ships a Friday afternoon release digest; Growth layers on a daily async stand-up written before 09:00 local and a monthly founder session; Scale adds a monthly executive review in written form plus a 60-minute call. Underneath all of it, the deliverables console is the live surface — every PR, every merged commit, every closed ticket, visible on a single page without you opening Slack.

Real questions, plain answers.
No billable hours.

Frequently asked — for the sceptical founder.

Got a question we didn’t cover?

Real questions, plain answers.No billable hours.