Build the product · Munich and Germany

Build an app or software that pays for itself

You have an idea or a process that needs software. Before you pick an agency, here's how the options compare, what drives the cost, and how a build led by a CTO works.

By Sanjeev Thapa3× founder & CTOUpdated Nov 2026

The short answer

Agency, freelancers or your own team? Each can work. What decides the outcome is who on your side decides what gets built, and what doesn't. I can do both parts: lead the decisions and deliver the build with my team and partners, from the first version to the handover.

01 / Your options

Four ways to get it built.

Agency

Good at
Delivering a defined scope fast
Risk
Builds what it's asked, not what you need
Fits when
The scope is clear and someone checks the work

Freelancers

Good at
Flexible, specific skills
Risk
Nobody owns the whole
Fits when
Someone senior leads them

Your own team

Good at
Long-term ownership
Risk
Slow and costly to hire before the product is proven
Fits when
The product is core to the business for years

A CTO-led build How I work

Good at
Decisions and delivery from one place
Risk
Depends on the CTO, so check the track record
Fits when
You want it built right without building a tech team first

02 / What drives the cost

The price is set by decisions, not hours.

ScopeWhat the first version must do, and what it doesn't. The biggest lever you have.
IntegrationsEvery system it has to talk to: ERP, payments, existing data, partners.
Open decisionsEvery question still open when building starts is paid for twice.
Changes mid-waySome are learning. Most are decisions that should have come first.
Running itHosting, updates and support after launch. Ask for this number before you sign.

03 / How a build with me works

One person accountable, from idea to handover.

  1. Diagnose

    What the business needs the software to do, and what success is worth in revenue, hours or margin.

  2. Decide what not to build

    A written scope for the first version, small enough to ship and useful enough to learn from.

  3. Build and ship

    My team and partners build it, I lead it. You see working software early and often, not a big reveal at the end.

  4. Measure

    Whether it does what it was built for, and what to build next because of it.

  5. Hand over or keep running

    Code, accounts and documentation in your company's name. Your own team takes over, or we keep running it.

04 / Warning signs

Whoever builds it, watch for these.

  • A fixed price before anyone asked what the app is for.
  • Code, accounts or servers in the builder's name instead of yours.
  • Months of work before you see anything running.
  • Every feature you mention gets a yes. Nobody says what to leave out.
  • No answer to "what does it cost to run and change after launch?"

05 / Questions

Questions people ask

Should I hire an agency, freelancers or my own developers to build an app?

It depends on how clear the scope is and who will make the technical decisions. An agency delivers a defined scope fast but builds what it is asked to build. Freelancers are flexible but need someone to lead them. Your own team pays off once the product is core to the business for years. In every case, someone senior on your side has to decide what gets built.

How much does it cost to build an app?

The honest answer is that it depends on scope, integrations, how many decisions are still open, and how much the plan changes along the way. The biggest lever is what you decide not to build in the first version. Get a cost based on a written scope, and be wary of a fixed price given before anyone has asked what the app is for.

Do you only advise, or do you also build?

Both. I can advise you while an agency or your own team builds, or deliver the build with my team and partners, led by me from the first decision to the handover. You don't need to go anywhere else.

Who owns the code?

Your company, in writing, including the source code, the accounts and the infrastructure. Investors and buyers check this in due diligence, so it should be settled before the first line is written.

06 / Read next

Related questions.

What do you want to build?

Tell me the idea or the process, and what it should change for the business. I'll tell you straight what the first version should be, and whether my team should build it.