How it starts
Your first two weeks, day by day.
The biggest offshore fear isn't the rate — it's the fog after you say yes. So here's the whole first fortnight, in writing, before you commit to anything.
Week one
Understand, set up, first code.
-
Day 1
The working session
Not a sales call — a working session. Your goals, users, constraints and deadline on one page. You meet the actual engineers, not an account manager. NDA signed beforehand if you want one.
-
Day 2
Everything in your name
Repos in your GitHub, environments in your cloud, a shared channel in your Slack. IP assignment is already in the contract you received after Day 1 — nothing lives on our side.
-
Day 3–4
The plan, priced
A milestone plan with the first two weeks fully detailed and the rest honestly rough — plus the running cost math at the published rate. You approve before build starts.
-
Day 5
First code, first demo
Something real runs by Friday: repo scaffold, CI, the first thin slice of the product deployed to a preview URL. The weekly demo rhythm starts here.
Week two
Rhythm, and your first exit ramp.
-
Day 6–9
The rhythm shows itself
Daily updates in your channel during your working hours. Brief us in your afternoon, wake up to progress. Questions arrive batched, not as a drip of pings.
-
Day 10
Demo two — with the numbers
Working software again, plus the honest ledger: hours used, hours projected, anything that surprised us. If scope should change, we say so now, not at invoice time.
-
Day 12
Retro, both directions
What's working, what isn't — including feedback for us. We adjust the process to your style, not the other way around.
-
Day 14
Your first exit ramp
Billing is weekly and cancel-anytime, so this is a real decision point, not a formality: continue, change shape, or walk away with your repos, your IP and two weeks of working software. Most continue. All keep everything.
Questions
Before day one.
What do I need to prepare before Day 1?
Just your head: goals, constraints, any existing material (spec, designs, codebase). We'll ask for GitHub/cloud access only after you've decided to proceed — and it's your accounts we set up, not ours.
What if I cancel after two weeks?
You keep everything: repos, environments, documentation, the plan and all working software — it was in your accounts from Day 2. You pay only for the hours worked. No lock-in is the whole point of weekly billing.
Is the first call really free?
Yes — and it commits you to nothing. A real person, usually a senior engineer, within 15 minutes of reaching out during studio hours.
Start the clock.
Day 1 is a 15-minute call with the people who'll build it.
Free · no obligation · a real person replies within 15 minutes