Generated code has no owner
When the model writes a file nobody read, nobody can fix it under pressure. The first production incident is when this becomes expensive.
AI MVP development · fixed scope, fixed date
Cursor, Lovable and v0 will get you a working screen by Sunday. They will not get you auth, a data model you can migrate, rate limits, an audit trail, or a bill you can predict. We build the part that survives contact with real users, on your infrastructure, with your code.
Workshops cost 1,500 PLN net per day and are deducted from the project if we sign within 30 days. If the workshop shows you do not need us, you pay for the workshop and nothing else.
AI MVP development is building the smallest version of a product a real user can use in production, with an AI capability at its core rather than bolted on. A prototype demonstrates intent; an MVP handles a paying customer. AppWave delivers one AI-driven process, an admin panel, up to two roles and one integration in 63 working days from the signed scope annex.
Why this exists
What stalls an AI-assisted build is rarely the feature. It is everything the model never wrote: the migration path, the permission model, the retry logic, the cost ceiling when a loop runs away at 3am.
When the model writes a file nobody read, nobody can fix it under pressure. The first production incident is when this becomes expensive.
An AI feature does not return yes or no. It returns something plausible. Handling hallucinations, edge cases and fallbacks is design work, not prompt work.
A demo costs cents. The same logic at a thousand users has a bill nobody modelled. We put the model account in your name from day one so you see it before it hurts.
What you get
Every one of them is written into the scope annex before anyone signs. Nothing is agreed mid-project.
Deployed on your infrastructure, ready for real users, not a staging link.
You watch it happen daily instead of seeing a handover at the end.
OpenAI, Anthropic and the rest bill you directly. We take no margin on tokens.
Defects traceable to our work are fixed free for a year after handover.
The numbers
We price the scope, not the hour. An hourly rate rewards the vendor for taking longer, which is the opposite of what you want from a first release.
Scope, price and date are agreed after the workshop and before the contract is signed. A written quote follows the first call.
How we work
Mateusz takes the call. All three founders build: frontend, backend and infrastructure, with nothing subcontracted.
You fill in the form, we talk the same working day. Mateusz Cieśliński picks up, not a sales rep.
Terms, payments, IP and confidentiality, all of it outside the scope. Your lawyer starts reading immediately instead of waiting a week for a specification.
One or two days at 1,500 PLN net per day, deducted from the project if we sign within 30 days. Remote for clients outside Poland; within roughly 100 km of Łódź we come to you. You leave with the scope, flow mockups and acceptance criteria written down.
A specific scope, a specific price, a specific date. Agreed before signing, never during the build.
A working version every two weeks. You have repository access from the first commit, so progress is something you check, not something you are told about.
Why us
Frontend, backend and infrastructure sit inside the company. Nobody is subcontracted, and the people who quote the work are the people who write it.
Three technical co-founders covering the full stack. No account managers, no delivery layer, no agency to hand you off to.
One web platform rather than native iOS and Android. A closed scope after the workshop rather than a growing backlog. One change up to four working hours is included.
Model bills land on your account from day one. You pay providers directly, and our incentive to over-engineer prompts disappears with the markup.
Guarantee
Working-scope guarantee
If the system does not meet the acceptance criteria written at the workshop, we fix it at no extra cost: no re-quote, no cap on revisions.
We can promise this because the acceptance criteria exist before signature, not during delivery. You know up front exactly what has to work for the project to be accepted.
Questions
Often you should, and we will say so on the workshop rather than sell you a project. AI tooling is genuinely good at the first working screen. It stops being enough at three specific moments: when cost scales linearly with users, when you need to swap the model for a cheaper or better one, and when an enterprise customer asks for a security review. At that point you rewrite under pressure, with users already in production.
Our first scope starts at 35,000 PLN net, which covers one AI-driven process, an admin panel, up to two user roles and one integration. Several processes with integrations on your side fall between 50,000 and 65,000 PLN. Complex domain logic and document processing at scale start at 80,000 PLN. We quote the scope after the workshop and before the contract, so the number does not move mid-project.
Three reasons, all checkable. There is no sales layer, because the three people who quote are the three who build. The scope closes after the workshop instead of growing through the project. Model costs go directly to your provider account with no margin from us. We are based in Poland, which lowers our cost base without changing who writes the code.
Our support windows are Central European Time. The top plan covers 8:00 to 20:00 CET seven days a week, which is 2:00 to 14:00 US Eastern and 23:00 to 11:00 US Pacific. We say this plainly rather than promise coverage we cannot staff. If you need US business-hours response, tell us on the first call and we will price it honestly or tell you we are the wrong fit.
It sits in your repository from the first commit. Full IP transfers after three months of a maintenance subscription, or immediately if you buy it out for 15% of project value.
The 63 working days run from the signed scope annex, not from first contact. The clock pauses while we wait on your decisions, access or content. That is why we ask for one decision-maker and replies within 24 hours: it is the only reason a specific date can exist. If the date starts slipping anyway, you hear it at the next fortnightly review, not on handover day.
One decision-maker for the whole project, replies within 24 hours, attendance at the workshop and at the progress reviews every two weeks, and access to the systems on your side. This is not paperwork. It is the only reason we can commit to a date.
Six things, and we name them up front so there is no argument at handover. Native iOS and Android apps, payment integrations, multi-language support, SSO and enterprise login, data migration from legacy systems, and a dedicated design system. We will build any of them, but as a separate scope with a separate quote, never quietly inside the base price.
Ten hours: the workshop, progress reviews and working calls. That genuinely covers a full project. Each additional hour is 180 PLN net, billed monthly. The limit applies only to meetings you attend, not to the time we spend building, testing and reporting.
We do cash plus equity: lower cash, a separate quote and a conversation about shares. Write to us and we will tell you honestly whether your project fits that model.
Fill in the form and we reply the same working day. Half an hour is enough to tell you whether this is worth building at all, and whether it is worth building with us.
Book a callNo cold calls. Mateusz picks up, one of the three founders.
office@appwave.dev+48 538 441 413appwave.dev
Off-the-shelf tools force you to compromise. We build a system around your process, with AI where it genuinely gives an edge.
Not another chatbot. An agent wired into your email, CRM and knowledge base that takes over repetitive work.
Repetitive work a machine does faster and error-free. AI only where it pays off.
Five subscriptions, zero order? We take over licences, access and security. One partner, one invoice.
Before you spend a single euro - we show, in numbers, where AI pays off and whether it's legal.
Your brand grows every day, even when you're doing something else. Agents prepare the content, you approve with one click.
Six ways to put AI to work. See where to start.