# About Metatable | Spec-Driven Software Generation

> We are building software generation for people who cannot safely judge code.

Metatable exists because prompt-based app builders made software feel easy to start, but hard to trust. We use specs as the source of truth so business owners can review what matters before code is generated.

The path: a plain prompt ("build a supplier tracking app for our team") becomes a spec (roles, records, permissions, workflow states, edge cases, deployment needs), which becomes a generated stack (PostgreSQL, Rust backend, Flutter frontend, deployment path, exportable code).

## 1. Why we exist

The hard part was never typing the prompt. Starting a software project with AI is easy now. The problem is knowing whether the result is complete, safe, maintainable, and aligned with how the business actually works.

That problem is sharper for non-technical owners. They can describe the workflow, but they cannot safely review a generated codebase. They need an artifact they can read before they trust the generated system. For us, that artifact is the specification. It carries the business logic, then code is generated from it.

## 2. Our point of view

Software should have a source of truth a business can read.

1. **Specs before code** — the business should understand what will be built before generation starts.
2. **Generated stack, not snippets** — database, backend, frontend, deployment path, and documentation need to stay connected.
3. **Owned code, not lock-in** — the output should be useful inside Metatable and exportable when the business needs it.
4. **Focused stack** — a narrower stack is easier to validate, ship, and explain than a broad set of half-connected choices.
5. **Honest limits** — frontend generation and iteration are still maturing. That should be clear before anyone trusts the product.

## 3. Who we build for

Metatable is strongest when the project has real records, rules, roles, and operational consequences.

- **SMB business owners** — need custom software without building a full dev team. What usually breaks: scattered workflows, vendor risk, and unclear handoff. What Metatable gives them: a readable spec, generated stack, deployment path, and exportable code.
- **Solo and micro-business owners** — need a way to turn the process in their head into working software. What usually breaks: prompt tools get close, then break when the app becomes real. What Metatable gives them: a structured path from requirements to an app they can run.
- **Freelancers and small agencies** — need professional client deliverables without prompt archaeology. What usually breaks: hard-to-maintain generated code and weak documentation. What Metatable gives them: a spec clients can review plus source they can hand off.

## 4. What we are building toward

A deployed app, not a tool you have to operate. The goal is not to hand you another tool to learn. It is to give you a running, owned application that came from a spec you can read.

The spec is the operating document underneath that outcome. It connects your requirements to generated code, deployment, and handoff, so the app stays maintainable instead of becoming a thing only its author understands.

## 5. Proof we can say today

Field notes, not inflated claims.

- 4,000+ registered users
- 5,000+ projects created
- 95% database generation success
- 72% backend deploy success (October 2025 funnel, 13 of 18 builds)

## Start here

Bring the workflow. We will help turn it into a spec.

- Build my app free: https://app.metatable.ai/signup
- Book a 15-min demo: https://cal.com/metatable/ai-dev-tool-demo