Skip to content

Glossary

MVP, prototypes, validation: precisely defined.

The core terms around MVP development, prototyping and product validation. Each entry answers the core question in one sentence first, then goes deeper.

10 terms shown

  • MVP (Minimum Viable Product)

    Product

    An MVP (Minimum Viable Product) is the smallest version of a product that delivers real value to real users while testing a business assumption.

    It is not a half-finished product but a deliberately reduced one: every feature has to answer an open question. The goal is learning under real conditions — before the budget for a full product is spent.

    Full definition: MVP (Minimum Viable Product)
  • Clickable Prototype

    Product

    A clickable prototype is an interactive design prototype — usually built in Figma — that feels like a real product but contains no code.

    Users click through real screens and flows before a single line of software exists. It answers the question “Does anyone understand and want this?” in days instead of months — at a fraction of development cost.

    Full definition: Clickable Prototype
  • Code Prototype

    Product

    A code prototype is a working software prototype that actually implements the technically riskiest core functions of a product — such as API integrations, data processing, or AI logic.

    Unlike a clickable dummy, it proves feasibility, not just comprehensibility. It is the right step when the biggest risk is not “Does anyone want this?” but “Does this even work?”

    Full definition: Code Prototype
  • Validation

    Product

    Validation means testing a business or product assumption with real users before building gets expensive.

    Behavior counts, not opinion: Do users get through the prototype? Do they understand the offer? Would they pay? A validation that stops an idea is not a failure — it prevents building the wrong product, which costs a multiple.

    Full definition: Validation
  • Fixed-Price Model

    Product

    A fixed-price model means: defined scope, defined result, fixed price — agreed before the project starts.

    The risk of overruns sits with the provider, not the client. At decivo, every module has a fixed price, from the clickable prototype at €3,500 to the code prototype at €12,500. Whoever takes longer carries it — which disciplines both sides toward a clear scope.

    Full definition: Fixed-Price Model
  • Vibe Coding

    AI

    Vibe coding is software development in which an AI generates the code from natural-language instructions and the human barely reviews the result in detail.

    This makes prototypes dramatically faster — and, without control, produces code nobody can maintain or extend. Legitimate for throwaway prototypes; viable for production systems only with systematic human review.

    Full definition: Vibe Coding
  • GEO & AEO

    AI

    GEO (Generative Engine Optimization) and AEO (Answer Engine Optimization) describe optimizing content so that AI systems like ChatGPT, Perplexity, or Google AI Overviews cite it as a source.

    The goal is citability rather than rankings: precise, self-contained answers, structured data, verifiable claims. If you don't appear there, you lose visibility — without seeing it in classic SEO metrics.

    Full definition: GEO & AEO
  • Service Role Key (Supabase)

    Security

    The service role key (in new projects: secret key, prefix sb_secret_) is Supabase's master key: it bypasses every Row Level Security rule and may read, change, and delete any row.

    It belongs on the server only. If it ends up in frontend code, a NEXT_PUBLIC variable, or the browser bundle, any visitor can read and overwrite the entire database — no matter how well the rest of the app is secured.

    Full definition: Service Role Key (Supabase)
  • Row Level Security (RLS)

    Security

    Row Level Security (RLS) is access control inside the Postgres database itself: policies decide per data row who may read or change it — for example “only the owner”.

    Without RLS enabled, every Supabase table the frontend can reach is open to anyone. RLS is the actual security layer of a Supabase app, not the login screen in front of it.

    Full definition: Row Level Security (RLS)
  • .env File & Exposed Secrets

    Security

    A .env file stores an app's secrets — API keys, database passwords, tokens — separately from the code.

    It must never end up in the browser and never be committed to the Git repository. Exposed secrets are one of the most common and most expensive weaknesses in AI and no-code apps: a single leaked key is enough to read databases, run up someone else's bills, or harvest user data.

    Full definition: .env File & Exposed Secrets

Ready for production-ready software?

Bring your project to a first call. We'll assess it honestly and recommend the right next step. 30 minutes, free of charge.

Book a first call