Process

How we work

Five steps from first conversation to production. Each step has a defined output you can take to your team — not a slide deck, but the actual artefact. We size every engagement so the next step is always reversible.

01

Discovery

1–2 weeks

A working session — not a sales pitch — to scope the problem, the data, and what success looks like. We map the workflow, identify where AI or blockchain can move the needle, and surface the assumptions everyone is making but not saying out loud.

What you get
  • A one-page problem statement signed off by your team
  • A data and systems audit (what exists, what is missing)
  • A short list of candidate use cases ranked by impact and feasibility
02

Design

2–3 weeks

A reference architecture, stack choice, and timeline you can take to your team. We decide what to build, what to buy, what to integrate, and what to defer. The design also names what we are not doing — scope discipline is how projects ship.

What you get
  • Reference architecture diagram and stack rationale
  • Cost model for build, hosting, and ongoing operations
  • Phased delivery plan with measurable milestones
  • Risk register with mitigations
03

Build

4–12 weeks

Direct founder involvement on the build — no account-management layer between you and the engineers. We ship in weekly increments to a staging environment your team can use, so feedback loops stay tight and surprises stay small.

What you get
  • Working software deployed to staging every week
  • Automated test coverage on critical paths
  • Documentation written as we build, not after
  • Read access for your engineering team from day one
04

Deploy

1–2 weeks

Cloud-native deployment on GCP or Ethereum, integrated with your existing stack. We handle the migration, the cutover, and the first weeks of production hand-holding. Your team learns the system by operating it with us, not by reading a runbook after we leave.

What you get
  • Production deployment with monitoring and alerting
  • Runbook for common incidents, written by the engineers who built it
  • Handover training for your engineering and ops teams
  • A defined support SLA for the first 90 days
05

Support

Ongoing (optional)

Ongoing model retraining, contract upgrades, and SLA-backed monitoring. We keep the system honest as your data drifts and your business changes. Some clients hand the system off entirely after the first quarter; others keep us on as a fractional team.

What you get
  • Quarterly model retraining and performance review
  • Smart contract upgrade audits where applicable
  • Defined response times for incident severities
  • A roadmap review each quarter — keep building, hand off, or sunset

Start with a Discovery call

A 45-minute working session to scope your problem and see whether we are a fit. No slides, no sales pitch.

Book a Discovery Call →