My fee depends on your revenue.
For the period set in the contract, I receive an agreed percentage of the app’s revenue. Once it ends, all revenue belongs to you.
Partnership
For founders who do not yet have the budget for a full app. I can build it for a small starting fee and take the rest of my fee as a percentage of revenue over an agreed period.
You pay a starting fee of 10% of the project quote. The rest of my fee is a share of the app’s revenue, limited by the contract in time and in amount. The services the app runs on, such as servers and the domain, are on you.
For the period set in the contract, I receive an agreed percentage of the app’s revenue. Once it ends, all revenue belongs to you.
| Standard model | Partnership model | |
|---|---|---|
| Upfront payment | the full quote | 10% of the quote |
| No revenue | cost incurred | the starting fee only |
| Risk | borne by the client | shared |
| My objective | delivering the scope | revenue growth |
| Settlement ends | at acceptance | after 5 years, the cap or a buyout |
The frame that applies to every contract. Within it, we set the details for your project.
From the submission to the end of the contract. The build itself runs as in every project of mine.
You describe the idea in the form: the problem, the users, the revenue model and the current stage.
Thirty minutes online. I ask about the market, your role and the plan for the first months after launch.
I tell you whether I will take the project on and explain why, including when the answer is no.
In writing: the scope of the first version, its standard-model quote, the share, the cap, and the buyout and sale terms. You pay the starting fee on signing.
A demo every week and a working version behind a link. The repository is on your account from day one.
The app reaches users. Every month you send a revenue statement, and I take care of maintenance and growth.
The share ends after 5 years, at the cap or on a buyout. From then on all revenue belongs to you. We can continue working together on standard terms.
In a partnership we both invest in the same product. That is why I select projects where I see a real chance of revenue. I assess them against four criteria.
You know the problem from your own experience or from the industry. That knowledge makes it possible to set the scope of the first version accurately and to talk to the right users from the start.
What shows it
You have first customers or a proven way to reach them. My fee depends on sales, so the channel to users matters as much as the product itself. It need not be large, a specific group of users is enough.
What shows it
The app earns from launch: through a subscription, sales or commission. The settlement is based on revenue, so models where it arrives only after years of building reach, such as advertising, do not suit this form of cooperation.
What shows it
You can give the project time regularly. I am responsible for the product, you for the market: talking to users, sales and decisions about where the product goes.
What shows it
The partnership does not fit every project. Sometimes another form of work suits better.
The standard model costs less over time, and all revenue stays with you from day one.
I take no equity in companies and do not fund their growth. You need an investor or a co-founder.
An app that does not sell generates no revenue to share. Choose the standard model or a ready no-code tool.
A model built on advertising and reach does not earn from launch. A revenue share cannot work before there is revenue.
Select the criteria your project meets, and see what to include in the submission.
The details of every partnership are set in the contract. These are the principles that always apply.
Write to me or book a call. The details of your project we discuss one to one.
You do. The repository is on your account from day one, and the economic copyright in the code passes to you when you accept the first version, under a written contract. The revenue share is the payment for it. My share concerns revenue only, not ownership.
I take no shares in your company and have no say in its decisions. I receive only an agreed percentage of the app’s revenue for a fixed period.
5 to 15% of revenue, depending on the scope of the first version and on what you bring to the project. It lasts at most 5 years from launch or until the cap is reached: three times the project’s standard-model quote in total. It ends at whichever comes first.
No. The contract can be signed with a company or with a private individual. As a private individual you have 14 days to withdraw from a contract concluded at a distance. If you ask for work to start sooner, the part done by then is settled at the standard-model quote.
You get the contract template before signing. We sign remotely, with a qualified electronic signature, or on paper. Each party’s liability is capped at the standard-model quote. If I cannot reach you for 30 days, I pause the work and the deadline moves by the length of the pause.
After launch I may show its name, screenshots and a description of my work. I name your company only with your consent, and I disclose nothing confidential. General components I use across projects stay mine: you get a perpetual licence to them that transfers with the app. Open-source libraries keep their own licences.
I treat submissions as confidential: I do not use ideas I do not build and do not pass them on. I can sign a non-disclosure agreement before the call. On request, I delete your submission.
It is 10% of the project’s standard-model quote, at least PLN 3,000 net, paid on signing. It covers part of the work on the first version and shows we both take the project seriously. It counts towards the cap and the buyout floor, so you never pay it on top of the agreed terms.
On net revenue, excluding VAT, from all payments for the app and its use: subscriptions, sales, transaction commissions and in-app advertising, less refunds. It does not include your company’s revenue outside the app, grants or investment. It does include revenue from the same app under another name or in another company.
Every month you send a statement of the app’s revenue, which the settlement is based on. On request, you give access to the source data, such as the payment dashboard.
Yes, at any time after launch. The amount is the average monthly share of the last 6 full months times the months left in the contract, at most 36. It is never lower than the standard-model quote less everything paid so far, starting fee included, and never more than what is left of the cap. A buyout ends the share together with the maintenance included in it.
The remaining share is either settled in one payment by the buyout formula or passes to the buyer. The choice is yours. The settlement is never lower than your share percentage of the part of the sale price that comes from the app, and never more than what is left of the cap. If you sell the company within 12 months of a buyout, we settle the difference up to that amount. If you sell the app itself, I have the right of first refusal on the buyer’s terms.
You send the revenue statement and the share for a month by the 14th of the next. Statutory interest is due on late amounts. If a payment is more than 60 days late, I may require a buyout of the share by the formula in the contract, and I pause development until it is settled.
You do, both during the build and after launch. I help choose services whose costs grow with the number of users.
Yes, for the whole contract. They cover setting up and monitoring the servers, backups, security updates, bug fixes and up to 8 hours of development a month. I respond to a critical failure within 1 business day and to other requests within 3. After the contract we can continue on standard terms.
You accept the first version within 7 days of handover: you either send your comments or accept it. I fix bugs in my code at no extra charge for as long as the share lasts.
Then we both lose: you the starting fee, your time and commitment, I most of the work put into the build. Beyond the starting fee you pay me nothing. That is why I select projects carefully.
I hand over all access and documentation free of charge and help pass the project to another developer. From that month your share drops by half until the contract ends, because it no longer covers maintenance.
I hand over the code written up to that point, together with the copyright. If you launch the app later, on your own or with someone else, the share applies under the contract, whenever the app starts to generate revenue. You can also settle the work done at the standard-model quote, less the starting fee, straight away and end the contract.