From Solopreneur to Web App in Seven Days — What Is Actually Achievable

Solopreneurs who want a web app built usually stand between two options. The first: a no-code tool like Bubble, Softr, or Glide. The second: an agency that plans with discovery workshops, six-figure budgets, and delivery dates several quarters out.
Both options have structural problems for solo businesses and tiny teams. No-code hits its ceiling earlier than the marketing copy suggests — as soon as custom data models, AI integrations, or specific workflows enter the picture. Agencies deliver clean technical work, but at timelines and prices that rarely make sense for a six-person business.
Between these two options lies a third, rarely discussed: **a senior-developer build at fixed price, short duration, that delivers real software — not a demo, not a prototype in the Storybook sense, but an application usable today and extensible tomorrow.** At aunomo.tech, that package is *The Prototype* (6,900 EUR, seven to ten days). This post describes what is actually included, what is not, and which use cases it pays off for.
## What The Prototype delivers in seven to ten days
The short version: a fully functional system with real database integration, real user workflows, and AI integration — ready to deploy with real data and real users.
What is included concretely:
-**Written scope document** before the build begins. Binding for both sides. Anyone who has worked with an agency without a fixed scope knows the value of this single page.-**Working system** with authentication, deployed on Vercel or comparable edge infrastructure. Subdomain or custom domain — your choice.-**Database integration** via Supabase (EU region, GDPR-compliant). Schema, row-level security, migration logic.-**AI integration** for at least one core workflow. LLM connection (OpenAI, Anthropic, Gemini, or Perplexity depending on use case), structured outputs, error handling.-**Real user workflows** — from login through the core function to the closing step. Not just one feature, but the end-to-end path.-**Full ownership (IP transfer).** Code, data, architecture documentation — all in your repository on the last day of the engagement.
What does "real software with real data" mean concretely? Three examples from current use cases:
**Example 1: internal tool for 5–20 users.** A consulting solo business with a low three-digit client base needs an internal CRM module that captures specific data requirements (engagement tracking, IP clauses, credit logic). Off-the-shelf CRMs do not fit; a no-code build would be brittle. *The Prototype* delivers the bespoke tool in seven days, runs in production today, can be extended via *The Build*.
**Example 2: Solar ROI Engine.** A solo energy advisor with pricing requirements for solar quotes: consumption-data input → amortisation calculation → finished PDF quote. The logic exists in his head and in an Excel file. *The Prototype* lifts that into a web app clients can use directly — branded to the advisor's identity.
**Example 3: MVP for internal pilot phase.** A founder with a validated business idea needs a first application for twenty beta users before investing in the full build. *The Prototype* is the vehicle for that pilot — real data, real user behaviour, defensible learning curve.
In all three cases, the delivery is production-usable at the end of the engagement. Not "it works on my machine", but "it runs on production infrastructure, has a clean onboarding flow, and the first real user can log in the same day."
## What is not included
The second important part is the honest list of what *The Prototype* does not cover in seven to ten days:
-**Complex multi-module architectures** with multiple sub-systems, separated services, microservice structures. Such setups belong in *The Build*, the full assembly package after a validated prototype.-**Payment integration with complex subscription logic.** A simple Stripe integration with one-time payment is included; multi-tier subscription models with proration and pause functions are build scope.-**Native mobile apps.** Web app with responsive design yes, native iOS/Android no — that belongs in a separate build track.-**Ongoing support after delivery.** After handover the code is your property. Maintenance, extension, new features are separate engagements (either *The Build* or a recurring model like *The Alliance*).-**Full compliance audits.** GDPR-baseline-compliant yes, end-to-end documentation for processing-on-behalf with thirty sub-processors no.
This list is not exhaustive — it is illustrative. For each engagement, the scope document explicitly defines what is in and what is out. The word "binding" appears at the top of the package description for exactly that reason.
## When The Prototype is the right choice
Four conditions should apply for *The Prototype* to produce maximum leverage:
**Condition 1: a clearly defined use case.**Not "a platform for solopreneur consulting", but "a tool that captures consulting engagements with IP-clause tracking and automatically sends monthly status reports to clients."
**Condition 2: validated assumption about users and value.**You know who will use the tool (your own staff, your own clients, your own client segments) and you have at least three concrete people who will work with it after delivery.
**Condition 3: willingness to take ownership.**You want the code in your own repository, deployed in your own Vercel account, with the option to extend it yourself or with another developer later. Anyone looking for a "please be my external developer forever" model is better served by a classical agency.
**Condition 4: realistic expectations about the seven-day logic.**Seven-day fixed-price builds work because the scope is tightly bounded. Anyone realising on day three "actually we also need a second module for X" is outside the scope — and the follow-up build (either a second prototype or *The Build*) is a separate decision.
## Crediting toward later full build
*The Prototype* is one hundred percent creditable against *The Build*. Concretely: anyone booking the full build after the prototype pays only the difference. The prototype is not sunk cost; it is the first tranche of a staged investment.
A practical side effect: for solopreneurs not yet sure whether their use case justifies the full build, *The Prototype* is the most honest pre-investment. Seven days later, you have not only a working system but also the data foundation to answer "is the full build even worth it?"
## The smaller and larger packages
*The Prototype* sits in a series of three build packages covering different depths:
-**The Spark** (2,490 EUR, 2–3 days) — a single tool for a clearly defined problem. Examples: AI quote generator, PDF-to-structured converter, email classifier. Standalone, not creditable.-**The Signal** (3,900 EUR, 4–6 days) — working prototype for investor demo or internal validation. Creditable against *The Prototype*.-**The Prototype** (6,900 EUR, 7–10 days) — this package description. Creditable against *The Build*.
If you are unsure which package fits: *The Audit* is a free thirty-minute orientation session in which we clarify exactly that — no sales pressure, no hidden follow-on costs.