Project Life Solutions Book a free 15-min call

1:1 coaching · 12 weeks

Ship your app to both stores in 12 weeks — and own every line of it.

A one-to-one program for founders and engineers who want a real, production mobile app live on the App Store and Google Play — built by you, with AI-assisted development. No agency retainer. No technical co-founder. No equity.

15 minutes, video or phone. Let's check if this program it's right for you.
No slide deck, no pressure — if it isn't a fit, I'll try to give you some advice on how to proceed anyways.

100%Code you own
2 storesApple + Google
0%Equity given away

Release checklist

v1.0.0
Developer accounts verifiedPhase 1
Sign-up and accounts workingPhase 2
Real testers on both platformsPhase 3
Paywall live, review submittedPhase 4
Live store links, both platformsPhase 5

Everything ships to your Apple Developer and Google Play accounts, from your repository. You could stop working with me in week 13 and keep shipping.

Why apps stall

The code isn't the hard part any more. The method is.

An AI assistant will write you a thousand lines of app on request. What it won't give you is a way of working: what to build first, how to tell output that's correct from output that merely runs, what to do when the attempted fix keeps failing, and the store compliance hurdles that come with it. A methodology is the difference between twelve weeks of progress and twelve weeks of running around in circles creating an unmaintainable mess — this is what the program will help you navigate.

The demo that can't scale

A prototype comes together in a weekend. Then auth, sync, payments and offline state arrive at once and the whole thing has to be rebuilt.

Can't afford high engineering fees?

The 2026 DACH freelancer study puts web developers at €91 an hour. Even part-time, a twelve-week build passes €20,000 — and at the end of it you still can't change your own app without them.

The last mile nobody warns you about

Privacy policies, store rejections, Google's 14-day closed testing rule, push certificates. This amounts to weeks of calendar time.

How the twelve weeks run

Five phases. Each one ends with something that works.

No phase ends with notes or a lesson completed. It ends with software running — on a device, in a store console, in front of testers. That is the only progress that counts here.

  1. 01

    Weeks 1–2

    Setup, specs & compliance

    You finish with: a running app connected to a live cloud database, and Apple and Google developer accounts through identity verification — the clocks that sink most first launches, started on day one.

  2. 02

    Weeks 3–4

    Accounts and identity

    You finish with: real users able to sign up, log in, edit their profile and stay logged in across restarts — on secure, production-grade foundations rather than a demo login screen.

  3. 03

    Weeks 5–7

    Your core value loop

    You finish with: the feature your app exists for, working end to end, in the hands of real testers on both iOS and Android. Google's mandatory 14-day testing period is already running by then.

  4. 04

    Weeks 8–9

    Money, notifications, device features

    You finish with: a working paywall, push notifications and device permissions in place, closed-beta feedback coming in, and your app submitted for production review.

  5. 05

    Weeks 10–12

    Store launch and hand-off

    You finish with: live App Store and Google Play links, store listings and privacy policies in place, review rejections cleared — and the hand-off that leaves you able to ship the next release without any help.

What's included

You don't start from a blank repository.

Week one begins on a working foundation — yours to keep, and to reuse on every app you build after this one.

A working starter project

A real, running app template — not a tutorial repo. Week one is spent on your product, not on wiring up the same foundations everyone wires up.

The development methodology

The daily build loop, written down: how each task is handed to the AI, checked, and closed out before the next one starts. This is the part that makes the twelve weeks hold together.

A field guide to your tools

Where to click and what to run, step by step, so a non-engineer can drive a professional development setup on day one without getting lost in it.

Weekly 1:1 sessions and async review

A fixed weekly working session, plus review of your work between sessions — so you're never stuck for a week waiting for the next call.

The methodology, the phase playbooks and the starter project are given to clients in the program. They aren't published here.

What you walk away with

Four things, and all of them are yours.

01

A published native app

Not a prototype. A native app on a battle-tested architecture, downloadable worldwide from both stores, with authentication, database sync, crash reporting and analytics running in production.

02

Every line of code and infrastructure

Your repository, your cloud accounts, your store listings, your API keys. No retainer to keep the lights on, no developer holding the deploy button, no equity traded for a skill you now have.

03

A working method, not a finished course

A spec-first workflow with Claude Code or Codex: how to write a spec a model builds correctly, how to review what it produces, and how to get unstuck without waiting for anyone.

04

A clean path through store review

Human Interface Guidelines, Google's 14-day closed testing requirement, privacy policies and data-safety forms, OAuth and push configuration.

This is for you if

  • You have one specific app or an idea that you want live, not a general interest in learning to code.
  • You can commit roughly 5-10 hours a week for twelve weeks, and you'll do the building yourself.
  • You're a domain expert with an idea, or an engineer who doesn't want to spend a year learning native mobile.
  • You want to keep shipping after week 12 without hiring anyone.

It's not for you if

  • You want someone to build it for you. This is coaching, not an agency — your hands stay on the keyboard.
  • Your idea needs hardware, a games engine, or heavy on-device machine learning.
  • You're still choosing between five ideas. Come back when one of them is the one.
  • You need it live in four weeks. Store review alone doesn't fit in that.
Daniel, who runs the coaching program, photographed against a plain wall

Who you'll be working with

Daniel — I've shipped many apps.

I have more than 12 years of experience, I have built software in very different industries that serves thousands of people. I have worked on mobile apps projects backed by Forbes where I performed as team lead.

I run the whole stack myself: React Native apps, the API and database behind them, release pipelines, store submissions, and the on-call pager when something breaks at midnight. It comes from practical experience and years of building software.

8 apps shipped 12 years building software

Where the evidence is

This program is new.

I won't show you testimonials I don't have yet. What I can show you is the work: three apps, live on the App Store and Google Play, designed, built, submitted and maintained by one person — running the same five phases you'd run.

Every claim on this page is something I've done, not something I've read about. Open any of the three and judge the result yourself.

Founding clients

You'd be one of the first, and it's priced that way.

I'm taking 5 founding clients at a reduced rate. In exchange I ask for something simple: your honest feedback each week, and — only if you're happy at the end — permission to use your launched app as a case study.

That's the trade. You get a lower price and my full attention while I have few clients.

2 of 5 founding places remaining

The investment

Three ways to get an app. Only one leaves you able to build the next one.

Pay someone to build it€91/hour

The DACH average for a freelance web developer in 2026. A part-time twelve-week build passes €20,000, before store submission — and every change afterwards is billable.

Find a technical co-founder20–50% equity

Forever, plus three to six months of searching, and the product stops the day they lose interest.

Build it yourself, guided A fraction of either — and you keep everything

0% equity. No retainer. No agency lock-in. Your repository, your store accounts, your revenue, and the ability to ship v2 without paying anyone.

Hourly rate: Freelancer-Kompass 2026, freelancermap's annual DACH freelancer study — €91/hour average for web developers, €103 across all IT freelancing. The €20,000 figure is that rate over twelve weeks at part-time pace. Equity range is a typical technical co-founder split, not a rule.

If after the first week you don't have a spec you believe in, I refund you in full and you keep the spec.

Questions people ask before booking

I've never written code. Is that actually fine?

Yes, and it's the most common starting point. You'll be writing specs and reviewing what the assistant builds from week one, and using tools that will allow you to test it without technical knowledge.

How many hours a week does this take?

5-10 hours of building, plus our weekly session. People who put in less than that finish late —.

What does it cost?

It's a single fee for the twelve weeks, payable monthly or in full, with no equity and nothing ongoing afterwards. Separately there are running costs you would have to pay: Apple's $99/year developer account, Google Play's one-off $25, cloud hosting, and an AI assistant subscription.

Who owns the app and the code?

You do, entirely, from the first commit. Repositories, cloud accounts and both store listings are created in your name. I take no equity, no revenue share and no licence.

Which technologies will I be using?

A modern cross-platform stack — a single codebase that ships to both stores — driven from VS Code with an AI assistant. We use the same stack throughout rather than touring five frameworks.

What if my app isn't approved?

Rejections are normal and planned for — phase 5 exists to clear them. Google's 14-day testing requirement is started back in phase 3 precisely so it can't hold up your launch. If review comes back with something after week 12, we fix it together.

Can I do this in a different time zone?

I'm in CEST timezone but I have no problem adapting to your schedule if needed. Sessions are booked to a fixed weekly slot; everything between sessions is async.

What happens after week 12?

You ship on your own — that's the point of of the program, you get your independence to run your app as you see fit.

Fifteen minutes is all it takes to get started.

Bring the idea in whatever state it's in and let's discuss whether this program is a good fit for you. If your idea is too big or complex, no worries, the whole point is to have a published MVP at the end of the program.

I'll answer all the questions you might have to see it the program is right for you.

Free 15-min callNo pitch — we just see if it fits Book