Machina Totalis
Process

How a project runs

Four steps, the same on every project. You see working software in the first week, you know the price before we start, and nothing ships without a senior engineer signing off.

Book a 30-minute callStart a project
  1. 01DiscoveryDay 1 to 2
  2. 02DesignDay 3 to 5
  3. 03DevelopWeek 1 to 3
  4. 04DeployWeek 4
01 DAY 1 TO 2

Discovery

A 30-minute call, then a written plan within 48 hours.

We start with your goals, your users, and your constraints. In a 30-minute call we ask the questions that decide the architecture. Within 48 hours you get a written proposal: the scope with explicit non-goals, the technical plan, the timeline, the fixed price, and the names of the engineers who will work on it.

You get

  • Written scope
  • Technical plan
  • Timeline
  • Fixed price
  • Named engineers

Tools

  • Zoom or Google Meet
  • Notion
  • Figma
02 DAY 3 TO 5

Design

Screens you approve before we build them.

Wireframes first, then high-fidelity screens and a clickable prototype in Figma, using your brand if you have one. You approve the design before production code starts, so the build matches what you pictured.

You get

  • Wireframes
  • UI designs
  • Clickable prototype
  • Design system

Tools

  • Figma
03 WEEK 1 TO 3

Develop

One-week sprints on a live staging link.

We build in one-week sprints and deploy to a staging link from day one. AI coding agents draft features and tests in parallel, each in its own branch. Tests run first. Then a senior engineer reads the change, runs it, and either merges it or sends it back with notes. You get a demo every week and can watch commits land in your repo.

You get

  • Working features
  • Weekly demo
  • Your repository with full history

Tools

  • GitHub
  • Claude Code
  • Playwright
  • Docker
04 WEEK 4

Deploy

Launch with monitoring on, then 30 days of fixes on us.

We deploy to production, set up the domain and SSL, and turn on error tracking, uptime checks, and alerts. A person deploys and watches every release. After launch, your 30-day fix warranty starts, and you get a runbook covering deploys, secrets, alerts, and rollback.

You get

  • Production deploy
  • Monitoring and alerts
  • Runbook
  • 30-day fix warranty

Tools

  • Railway or your cloud
  • GitHub Actions
  • Error tracking
Communication

You always know where it stands

  • Shared Slack channelAsk questions and get answers from the engineers building your product, not a go-between.
  • Weekly demoEvery week we walk you through what shipped, on the real staging link.
  • Live staging from day oneClick through the product as it is built and share it with your team.
  • Commits you can seeThe repo is yours, so every change lands where you can read it.
Quality

Every change crosses the same gate

AI agents write code quickly and are wrong often enough to matter. This is what stands between their drafts and your users.

  1. 01

    Tests run first.

    Every branch comes back with tests, and they run before a person spends a minute on it.

  2. 02

    A senior engineer reads every diff.

    They run it, and if they would be embarrassed by it in production, it goes back with notes.

  3. 03

    A person merges.

    Nothing merges because a model said it was fine.

  4. 04

    A person deploys.

    Agents cannot deploy, delete, or touch production on their own.

  5. 05

    It is written down.

    Every project ends with a runbook in the repo for whoever inherits it.

A fleet of AI coding agents with a human gate.

Read the case study
Timelines

Typical timelines

Ranges from past projects. Your proposal states your dates.

  • Project type
    Free 7-day build
    Typical timeline
    7 days
    Phases
    Discovery 1 day, build 5 days, deploy 1 day
  • Project type
    Landing page or website
    Typical timeline
    1 to 2 weeks
    Phases
    Design 3 days, develop 4 to 7 days, deploy 1 day
  • Project type
    MVP
    Typical timeline
    2 to 4 weeks
    Phases
    Discovery 2 days, design 3 days, develop 2 to 3 weeks, deploy 2 days
  • Project type
    Web application
    Typical timeline
    4 to 8 weeks
    Phases
    Discovery 3 days, design 1 week, develop 3 to 6 weeks, deploy 3 days
  • Project type
    Mobile app (iOS and Android)
    Typical timeline
    6 to 10 weeks
    Phases
    Discovery 3 days, design 1 week, develop 4 to 8 weeks, testing 1 week
  • Project type
    Larger systems
    Typical timeline
    8 to 12 weeks
    Phases
    Discovery 1 week, architecture 1 week, develop 5 to 9 weeks, testing 1 week
Typical timelines
Project typeTypical timelinePhases
Free 7-day build7 daysDiscovery 1 day, build 5 days, deploy 1 day
Landing page or website1 to 2 weeksDesign 3 days, develop 4 to 7 days, deploy 1 day
MVP2 to 4 weeksDiscovery 2 days, design 3 days, develop 2 to 3 weeks, deploy 2 days
Web application4 to 8 weeksDiscovery 3 days, design 1 week, develop 3 to 6 weeks, deploy 3 days
Mobile app (iOS and Android)6 to 10 weeksDiscovery 3 days, design 1 week, develop 4 to 8 weeks, testing 1 week
Larger systems8 to 12 weeksDiscovery 1 week, architecture 1 week, develop 5 to 9 weeks, testing 1 week

Start with a 30-minute call

You leave with a clear plan, whether or not you hire us.
Book a 30-minute callStart a project