# You can vibe-code a demo in a weekend. Shipping it is another job. > You can vibe-code a demo in a weekend. Shipping it is a different job. Fixed scope, a fixed date, and your repository from the first commit. - **Canonical URL:** https://appwave.dev/en/services/mvp-ai - **Language:** en --- 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. - Scope agreed before signing - 63 working days - Your repository from day one 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. ## What AI MVP development actually means 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. ## The demo is the easy 20%. Production is the other 80%. 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. ### 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. ### Probabilistic features fail differently 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. ### Token cost scales with users, not with you 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. Not sure whether you need a fixed project or an ongoing team? Compare both in the calculator → ## Four things you hold after 63 working days. Every one of them is written into the scope annex before anyone signs. Nothing is agreed mid-project. ### A system in production Deployed on your infrastructure, ready for real users, not a staging link. - One AI-driven process - Admin panel and up to two roles - One integration with a system you already run ### Your repository from commit one You watch it happen daily instead of seeing a handover at the end. - Access from the first day - Full IP after three months of maintenance - Buy it out earlier for 15% of project value ### Model costs on your account OpenAI, Anthropic and the rest bill you directly. We take no margin on tokens. - Billed by the provider, not by us - Zero markup on inference - You see every dollar as it is spent ### Twelve months of warranty Defects traceable to our work are fixed free for a year after handover. - On any support plan, and on none - Warranty fixes never consume support hours - Excludes new features and third-party code changes ## Fixed scope, fixed date, quoted before you commit. 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. | Value | What it is | How we know | | --- | --- | --- | | 63 days | Working days, from a signed scope | Roughly three calendar months. The clock stops while we wait on your decision, access or content, because those are the only variables we do not control. | | 5 days | From first contact to first commit | Day one a 30-minute call, day two the framework agreement with your counsel, days three and four the workshop, day five the scope annex is signed. | | 4 stages | Payment tied to milestones | 15% on signature, 25% and 25% on two milestones defined in the annex, 35% on acceptance. You know in advance what has to work before an invoice goes out. | | 1,500 - 4,000 PLN | Monthly support after handover | Three plans, chosen at handover. Start at 1,500 PLN with no development hours, Growth at 2,500 PLN with five hours a month, Partner at 4,000 PLN with twelve. None of them is mandatory. | Scope, price and date are agreed after the workshop and before the contract is signed. A written quote follows the first call. ## Five days to start, then 63 days of building. Mateusz takes the call. All three founders build: frontend, backend and infrastructure, with nothing subcontracted. ### Day 1 — Form and a 30-minute call You fill in the form, we talk the same working day. Mateusz Cieśliński picks up, not a sales rep. ### Day 2 — Framework agreement with your counsel Terms, payments, IP and confidentiality, all of it outside the scope. Your lawyer starts reading immediately instead of waiting a week for a specification. ### Days 3-4 — Workshop 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. ### Day 5 — Scope annex and signature A specific scope, a specific price, a specific date. Agreed before signing, never during the build. ### Days 6-68 — 63 working days of building 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. ## Three founders build it. There is no layer in between. Frontend, backend and infrastructure sit inside the company. Nobody is subcontracted, and the people who quote the work are the people who write it. ### The people who sell are the people who build Three technical co-founders covering the full stack. No account managers, no delivery layer, no agency to hand you off to. ### Scope closes before the contract opens 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. ### We take nothing on your model spend Model bills land on your account from day one. You pay providers directly, and our incentive to over-engineer prompts disappears with the markup. ## You are not paying for a promise. You are paying against acceptance criteria. 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. - Twelve-month code warranty: defects traceable to our work are fixed free after handover. - Applies on any support plan and on none. Warranty fixes never consume your support hours. - The 63-day clock stops while we wait on you. New features are not covered. ## The questions founders ask on the first call. ### Why not just build it myself with Cursor or Lovable? 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. ### What does an AI MVP cost? 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. ### How can it cost less than a US agency? 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. ### What are your support hours in my timezone? 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. ### Who owns the code? 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. ### What happens if you miss the deadline? 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. ### What do you need from us? 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. ### What is not included in the base scope? 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. ### How many meetings are included? 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 are a startup with no budget. Any other way? 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. ## Thirty minutes, and a straight answer. 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. No cold calls. Mateusz picks up, one of the three founders. --- ## About AppWave AI software house from Łódź, Poland. We build custom AI software, automation agents and web applications. We co-create them with the client and guarantee every system we deliver. - **Legal name:** AppWave sp. z o.o. - **Address:** ul. Kolumny 147E/1, 93-611 Łódź, Poland - **Phone:** +48 538 441 413 - **Email:** office@appwave.dev - **Business hours:** Monday-Friday, 09:00-17:00 - [Free consultation](https://appwave.dev/en/appointment)