MVP ready to run · fixed scope, fixed date

You can vibe-code a demo in a weekend.Shipping it is another job.

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
  • Up to 3 months
  • Your repository from day one

Workshops run up to 3 days at 1,200 PLN net per day. The project itself starts at 15,000 PLN net, and if we stay on for the build we deduct the workshop from the invoice. No deadline on your decision. If the workshop shows you do not need us, we will say so and you pay for the workshop and nothing else. If you walk away for your own reasons, you pay for the days you got and nothing beyond them.

5.0 / 5
Guaranteeon every system we deliver
up to 45 minfree consultation, no obligation

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 up to 3 months from the signed offer.

Why this exists

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.

01

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.

02

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.

03

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 →

How we work

Six days to start,then up to 3 months of building.

Mateusz takes the call. All three founders build: frontend, backend and infrastructure, with nothing subcontracted.

  1. Day 1

    Form and a call of up to 45 minutes

    You fill in the form, we talk the same working day. Mateusz Cieśliński picks up, not a sales rep.

  2. 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.

  3. Days 3-5

    Workshop

    Up to 3 days at 1,200 PLN net per day, deducted from the invoice if we stay on for the build. Remote for clients outside Poland; within roughly 100 km of Łódź we come to you. You leave with the scope, a process map, a proposed technology, the data flow and acceptance criteria written down, and that document is yours even if you pick someone else.

  4. Day 6

    Offer and signature

    Everything in one document: the costs, exactly what we do and the dates of each stage. Agreed before signing. The price changes only if the scope changes, and we always agree that with you first.

  5. Up to 3 months

    Up to 3 months of building

    We build in modules. After each one we show the result and collect your comments. You have repository access from the first commit, so progress is something you check, not something you are told about.

up to 3 months

We trim the scope to this number, not the number to the scope.

What you get

Four things you holdafter 3 months.

Every one of them is written into the offer 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
  • Economic rights transfer as each module is paid
  • Our own components stay ours, but the licence is perpetual and transfers with the project
  • No surcharge, the transfer fee is in the price

Model costs on your account

OpenAI, Anthropic and the rest bill you directly. We take no margin on tokens.

  • Billed by the provider, or included in the SLA plan
  • 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 SLA plan, and on none
  • Warranty fixes never consume SLA hours
  • Excludes new features and third-party code changes

The numbers

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.

From a signed offer
up to 3 mo.
Three calendar months at most. The clock stops while we wait on your decision, access or content, because those are the only variables we do not control.
From first contact to first commit
6 days
Day one a call of up to 45 minutes, day two the framework agreement with your counsel, days three to five the workshop, day six the offer is signed.
Payment per module
15% / 85%
A 15% deposit before each module starts and 85% once it is delivered. Most of the money pays for something that already works.
Monthly support after handover
800 - 6,000 PLN
Three SLA plans, chosen at handover. Start at 800 PLN with a response within 1 working day, Standard at 2,500 PLN with a response within 4 working hours and up to 5 hours of small changes a month, Extended at 6,000 PLN with a response within 1 hour and up to 15 hours of changes. None of them is mandatory.

All amounts are net. Scope, price and date are agreed after the workshop and before the contract is signed.

Evidence

roughly one fifth of our scope

The client wanted to build the core of the system as their own component, before anyone had checked whether the product was needed at all.

We advised against building the core from scratch and pointed to a proven external supplier.

The client validated the hypothesis on time, and is building the own component after validation, not before it.

Why us

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.

We take nothing on your model spend

Cost

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

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 SLA plan and on none. Warranty fixes never consume your SLA hours.
  • The 3-month clock stops while we wait on you. New features are not covered.

Start with a call,and a straight answer.

Fill in the form and we reply the same working day. A call of up to 45 minutes is enough to tell you whether this is worth building at all, and whether it is worth building with us.

Book a call

No cold calls. Mateusz picks up, one of the three founders.

  • 5.0 / 5 - 16 reviews
  • 12 months of warranty - defects in what we built are fixed at no extra charge.
  • You talk to the owner, not a salesperson

office@appwave.dev+48 538 441 413appwave.dev

Questions

The questions founders askon the first call.

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 15,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 moves only if the scope does, and we always agree that with you first.

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, or into the SLA plan, with no margin from us. We are based in Poland, which lowers our cost base without changing who writes the code.

Our support runs on Central European Time. Depending on the SLA plan, we respond within 1 working day, within 4 working hours or within 1 hour. 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.

The 3 months run from the signed offer, 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 module review, not on handover day.

One decision-maker for the whole project, replies within 24 hours, attendance at the workshop and at the review after each module, 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.