How fast can you ship an MVP?

21 calendar days from kickoff to production deploy on the 21-Day MVP path. Custom Software builds run 6 to 26 weeks depending on scope.

How much does an MVP cost?

21-Day MVP from $5,000 USD. Custom Software Development from $11,000. AI Development from $7,000. Final quote depends on scope and integration count.

What stack do you use?

Default stack: Next.js, TypeScript, Node.js, Python, PostgreSQL, AWS, Stripe, Clerk, OpenAI, Anthropic Claude.

Do you work fixed-price or time-and-materials?

21-Day MVP is fixed price by design. Custom Software is sprint-based pricing with scoped milestones. We do not bill on open-ended T&M because it incentivises the wrong things.

You. Full code ownership transferred on launch. Repo handed over. Cloud, vendor, and platform accounts moved into your name. We do not retain IP.

What if scope changes mid-build?

In the MVP path, scope changes after Day 2 are Day 22 work. In Custom Software, scope changes within a sprint are handled at sprint-plan; mid-sprint they are deferred to the next sprint. The discipline is what keeps the engagement honest.

Can we extend the engagement?

Yes. Custom Software engagements often run for multiple quarters. Each extension is a new SOW. We preserve team continuity where possible.

What about your team timezone?

Distributed team across UTC plus 1 to UTC minus 5. Engagements run in your timezone with synchronous weekly touchpoints. Async work fills the rest.

Yes. Product and UX design included in every engagement. Brand-design (logo, identity) is not our service line; we partner with brand firms for that.

Yes. React Native and Flutter for cross-platform. Swift and Kotlin where the engagement justifies native. Apple App Store and Google Play submission included where applicable.

What about quality assurance?

QA is built into every sprint, not bolted on at the end. Test coverage gates. Pre-prod manual QA pass before each release. Internal pen-test on every build, external pen-test for regulated.

How do you handle disputes or disagreements?

We work in short cycles with frequent demos so misalignment surfaces fast. Disagreements on direction are decided at the weekly Tuesday demo with the stakeholder. We push back when we believe the brief is wrong but we do not stonewall.

Last updated: 09 June 2026

How We Work

Two engagement paths: a fixed 21-day productised MVP, or a 6-to-26-week custom build. Both ship with two-week sprints, weekly demos, test-coverage gates, and a runbook handed over on launch. This page covers the cadence, the artifacts, and the discipline.

Book a free 45-minute scoping call

We send a written scope and price within 3 business days of the call. No obligation either way.

Overview

Engagement at a glance

The essentials of how we run an engagement — cadence, team shape, communication rhythm, and what lands in your hands at handover.

21-Day MVP path

Day 0 kickoff · Day 2 scope lock · Day 7 skeleton · Day 16 core build · Day 21 launch

Custom Software path

2-week sprints · weekly demos · staging deploy every sprint · hardening sprint pre-launch · 2-week dual on-call post-launch

Team shape

1 product lead · 1 to 4 senior engineers · 1 designer · 1 on-call rotation

Communication

Slack Connect or your channel · weekly Tuesday demo · sprint-end retro · Loom for async updates

Deliverables

Code · tests · CI/CD pipeline · staging environment · production environment · runbook · architecture record

Handover

Day N: live production code · accounts in your name · runbook · dual on-call for 2 weeks

Engagement paths

Two engagement paths

Most prospects fit one of two paths. We tell you which at the scoping call. We do not run hybrid engagements that try to be both.

Productised

21-Day MVP

Productised. Fixed 21 calendar days. Fixed scope locked on Day 2. Fixed price. For first-version builds where speed-to-market beats feature count.

From $5,000

View service →

Bespoke

Custom Software Development

Bespoke. 6 to 26 weeks. Scope flexes inside two-week sprints. Price is sprint-based or milestone-based. For production systems where scope cannot fit into 21 days.

View service →

The process

Five phases from discovery to Day 22+

Same discipline in both paths. Different cadence, same artifacts.

Day 0–2 · Week 1Phase 1 of 5

🔍Discovery and scope

Discovery is the difference between a build that ships and one that drifts. Every engagement starts with a discovery phase. The shape of it depends on the path.

MVP path discovery (Day 0 to Day 2). One working session with the founder. We co-write the one-page scope: target user, core workflow, success metric, default stack, integrations. Scope is locked at end of Day 2.
Custom Software discovery (2 to 4 weeks). Stakeholder interview round. Existing-system audit. Data audit. Regulatory scope mapping if applicable. Architecture decision records (ADRs). Output: scoped milestones with estimated durations.
We do not run discovery as a separate paid contract. It is part of the engagement. If after discovery we determine the engagement does not fit our service lines, we refund unspent budget and refer you to a firm that does.

Discovery · Phase 1

Communication and rhythm

We communicate the way we work: written, structured, and consistent.

💬

Slack Connect or your channel

Day-to-day async. We respond in your working hours.

📅

Weekly Tuesday demo

45 minutes. Working software, not slides. Decisions taken with the stakeholder, not after.

🔄

Sprint-end retro

30 minutes. What worked, what did not, what changes next sprint.

🎥

Loom for async updates

5-minute Loom video where written would take 20 minutes to read.

🚫

No PowerPoint status reports

Status is the demo plus the sprint board. We do not produce decks to make status feel produced.

Expectations

What we do not do

Three things we want clear so the scoping call does not start with crossed expectations.

No junior placement

Senior-only delivery. We do not staff engagements with juniors to subsidise margin.

No body-shop billing

We bill against outcomes and sprints, not hourly rate cards.

No 'agile theatre'

Sprints exist to ship working software, not to perform process. If a ceremony does not add value, we cut it.

Frequently asked questions

Typically 2 to 4 weeks from scoping call to kickoff. We do not double-book the team. If we cannot start within 4 weeks, we say so at the scoping call.

READY TO SHIP?
BOOK A 30-MINUTE CALL.

Book a Free Call

<45mAVG. RESPONSE

FixedPricing

2 to 8WEEKS DELIVERY