Skip to content

Process

Four steps, and you can stop after the first.

Most of what goes wrong in a software project goes wrong before anyone writes code — in a scope nobody wrote down, or a price that moved. These four steps exist to close both, and the first one is free.

How we work.What happens, what it commits us to, and what you keep.

Step 01

Thirty minutes.

Free. No pitch. Often we tell you it isn’t software you need.

We don’t charge for it, and we don’t follow it with a sequence of emails. If the answer is a spreadsheet, a change to how you work, or a tool you already pay for, we say so.

You keepA clearer problem, whether or not you hire us.

Step 02

Scope, fixed.

A written scope and a fixed price. If we’ve underestimated, that’s our problem.

The price doesn’t move because the work turned out harder than we thought. It moves only if you change what you asked for — and then you see the new number before anything is built.

You keepA written scope and one price, before any work starts.

Step 03

Build, in the open.

You see it weekly. Nothing is a surprise at handover.

Something you can open, every week — not a status update. Weekly is slow enough to be real progress, and early enough that a wrong turn costs a week rather than the project.

You keepA working build every week, and somewhere to say “not that”.

Step 04

Handover, full IP.

The code is yours. No lock-in, no dependency by design.

The code, the accounts and the documentation all transfer to you. We don’t hold the keys as leverage, and nothing is built so that only we can look after it.

You keepFull ownership, and the ability to hire someone else next time.

The decision filter.Eight questions we run every project through. The third one is the expensive one.

  1. 01Does this genuinely help someone?
  2. 02Are we solving the real problem, or only the requested symptom?
  3. 03Would we still recommend this if it made us less money?
  4. 04Is the solution sustainable and maintainable?
  5. 05Would we be proud to put our names on it?
  6. 06Does this help our people grow?
  7. 07Are we making technology easier for the person using it?
  8. 08Are we using AI responsibly, with human ownership of the outcome?

Values are only useful when they change a decision. These are the testable form: run a project through them and you get an answer.

What we won’t do

The list that turns work down.

  • Build software only because the client has money
  • Implement every request without understanding why
  • Ship low-quality AI-generated work and call it finished
  • Use complexity to make clients dependent on us
  • Treat people as tickets, leads, or invoices

Start with the thirty minutes.

It’s free, there’s no pitch, and you can stop there. That’s the whole point of putting it first.

Book the thirty minutesjeikudev@gmail.com