How we build / The process Five steps, one definition of done

We build in the open, in plain language.

One person runs your project. You know the price and the date before we start, and you own everything we make, from the first line of code.

01 / The process

Five steps, no surprises.

Every build runs the same way, so you always know what is happening and what comes next.

  1. 01

    Scope

    We pressure-test the idea, map the smallest version worth building, and agree the price and the date.

    Week 0
  2. 02

    Design

    We design the product and the architecture together, so the build starts from a clear picture.

    Weeks 1–2
  3. 03

    Build

    One lead, plus the specialists it needs, builds it in the open and ships working software every week.

    Weeks 2 on
  4. 04

    Launch

    We ship to production, hand over the code and accounts, and make sure it holds under real use.

    Launch
  5. 05

    Run

    We keep improving it in production, or hand it over clean. You own it either way.

    After launch

02 / Ego Eimi vs the alternatives

Three ways to get software built.

The same questions decide how a build goes. Here is how each path tends to answer them.

Hiring a developer yourself A typical agency Ego Eimi
Who owns the code Usually you, if the contract says so and they hand it over Often the agency, with the platform and accounts held on their side You, from the first line, including infrastructure and accounts
Price model Hourly or salaried, open-ended An estimate that moves as the work moves A single fixed price, set before any code
Who is accountable You manage the work and carry the risk An account manager, with the build a layer below One lead who owns the outcome end to end
What happens after launch It depends on whether they stay A retainer you may not be able to leave We keep improving it, or hand it over clean. You own it either way
Security As strong as the person you hired Varies by team and is rarely shown to you Built in, with the work done in the open so you can see it
Time to start Weeks to hire and onboard the right person A sales cycle, then a queue A price and a date within a day

02 / Three principles

  1. 01

    We build what people want.

    We build past the brief, watching how customers actually use the product and refining it long after launch.

  2. 02

    We own the outcome.

    Success is what your software does for your business, not billable hours. When something breaks, fixing it is our job.

  3. 03

    We make it compound.

    An asset that makes the work around it stronger and grows more valuable over time. Yours from line one.

03 / The guarantee

What you can hold us to.

Four things we commit to on every build, before any code is written.

01

Fixed price

Agreed before we start, in writing. No billable-hour surprises and no scope games.

Quoted up front
02

Fixed deadline

A delivery date we commit to, not a range. You can plan the launch around it.

Committed, not estimated
03

You own everything

The code, the infrastructure, and the accounts are yours from the first line. There is no lock-in.

Yours from line one
04

We own the outcome

We measure ourselves by what the software does for your business. If it breaks, fixing it is our job.

Outcomes over hours

04 / Definition of done

  • ✓Live in production, under real use
  • ✓Code, infrastructure and accounts handed to you
  • ✓A walkthrough so your team can run it

No retainers you cannot leave, and no platform you cannot export. The work is yours, and we are happy to keep improving it or to step back once it ships.

05 / Common questions

How long does a build take?

A Forge build runs four to eight weeks at a fixed scope, price, and deadline. A short Audit before it takes about one to two weeks.

What does “done” mean?

Live in production under real use, with the code, infrastructure, and accounts handed to you, plus a walkthrough so your team can run it.

What if the result does not meet what we agreed?

We remediate it for free against the signed acceptance criteria, time-capped at about six weeks. New requests become a change order.

Do I own the code?

Yes, from the first line of code: the code, infrastructure, repository, documentation, AI prompts, evals, deployment, and IP. There is no lock-in.

How is the price set?

Fixed and agreed up front, before any code is written. There is no hourly billing and no open-ended estimate.

Can I stop after the audit?

Yes. You can stop after any step. The Audit fee is credited toward a build if you continue.

05 / Your build

Taking on new builds

Have something in mind?

Tell us what you're making. We reply within a day with a fixed price and a date.

Start a conversation See the work