What a Multiplatform App Really Costs: A Transparent Day Rate

One point of contact, a clear day rate, a fast prototype, then useful iterations.

Instead of an agency quote running into six figures, I work at a transparent day rate and tell you honestly what fits your budget. Day rate: €500.

Repair order

Nº ····

Drop-off

Your day, 9:00

Ready

19:00

You collect

The fix running on your phone, and the change in your source code.

Keep this stub

Nº ····

Day one

€500 excl. tax

Book day one

Remote day rate

€500excl. tax

Solo since 2008, I make product and technical calls quickly because there is no agency layer sitting between you and the code.

You collect

  • An honest estimate of what fits your budget, with a clear line on what moves to phase two.
  • A fast working prototype that validates the core of the app before you invest further.
  • Native iOS and Android development with a single point of contact from quote to delivery.
  • Iterations scoped in days of work, with no agency markup and no middle layer.

Repair order

  • Where the six-figure quotes come from

    Agency quotes for an app across several platforms commonly run from $70,000 to $300,000. That figure adds up the backend, design, project management, and several people, each carrying their own margin. For a founder or an SMB, the budget and timeline become hard to predict, and a large share of the cost goes into coordination rather than code.

  • A day rate, not an opaque envelope

    I charge €500, with no agency markup. You follow the work in identified days and keep control of what gets prioritized. That transparency makes the budget predictable: you know what a feature costs before you start it, and you can pause or push it whenever you want.

  • Decisions move fast with one person

    Working solo, product and technical decisions happen directly with you, without a relay or a long kickoff cycle. That cuts the hidden cost of communication, which is often what inflates quotes with many contributors. You talk to the person who writes the code, so a question gets an answer the same day instead of a week later.

  • Prototype first, then iterate

    I start with a working prototype that proves out the core of the app, then iterate from real feedback. This limits the risk of paying for a large build before checking that the idea holds up. And I tell you plainly what fits a given budget, even if that means deferring some features to a later phase.

Frequently asked questions

Your next ticket

The next free day is on the calendar. Start with a free call if you want to talk it through first.

Book a free 20-min call

Keep this stub

Nº ····

Day one

€500 excl. tax

Book day one

Or leave a note at the counter

Describe your project. I answer right away in the chat when I am available, within 24 hours otherwise.