features

One plan. A complete, running application built from it.

You describe how your business works. Metatable writes it down as a plan you can read, then builds everything from it — the database, the rules, the screens, the hosting. Change the plan and the software follows. Export the code anytime.

specification.prd source of truth
Inventory Operations App
roles

Owner, warehouse manager, purchasing editor, read-only accountant.

records

SKU, warehouse, supplier, purchase order, stock movement, reorder rule.

rule: create purchase order when stock falls below threshold.

permission: only owners approve supplier changes.

01 · the plan

It starts with a plan you can read — not a pile of prompts.

Before anything is built, Metatable writes down your roles, records, rules, and edge cases in plain language. You read it, correct it, approve it. The app is built from that document — and when your business changes, you change the document, not the code.

For the technically minded: it is a real spec, and it stays the source of truth.

Product Requirements Document approved
1. Product overview

Replace spreadsheet-based vendor tracking with a running application.

2. Primary workflow

Capture request, assign owner, validate data, approve, report status.

3. Access rules

Editors update operational records. Owners manage users and approvals.

4. Edge cases

Duplicate supplier, expired contract, missing approver, delayed renewal.

02 · what you get

What you actually get.

A complete, running application — typically live in about 30 minutes. Not a demo and not screens over a spreadsheet. Here is every piece, exactly as it appears in the platform.

generated documentation

Your software, written down.

The full architecture of your application in plain language — every workflow, rule, nuance, and use case. You approve it before anything is built, and it stays up to date as the app changes. New hire? Hand them the document.

Client Service Hub
Specs Preview Settings
Subscribe Publish
…and shared document links. Later versions cover service request submission and broader communication history. Sound right?
Right
Should reminders be sent by email?
not now
v1 building v1
SpecsGenerating specs.
PRD approved
Databaseupcoming
Backendupcoming
Frontendupcoming
Database Spec: Defining tables and relationships…
Make changes, add new features or ask for anything
General Database Backend Frontend
Client Service Hub PRD
1. Product Overview
1.1 Product Vision
Client Service Hub is a client-facing portal for a service business that gives customers a simple, trusted place to review their service relationship after sign-in. The product brings together appointments, billing records, and shared document links into one responsive web experience.
1.2 Problem Statement
Current problem: Customers rely on scattered emails, calls, and manual follow-up to understand upcoming service appointments.
Why now: Service businesses need a clearer self-service experience that reduces missed appointments and repetitive support work.
Success signals: Customers reach a useful dashboard immediately after sign-in and review details from any device.
generated database · PostgreSQL

A real database, built from your plan.

Every record your business tracks — customers, orders, stock, suppliers — stored with proper structure and relationships. Not rows in a spreadsheet: the same class of database banks run on.

Specs Preview Settings
Subscribe Publish
General
App settings
Domain
Server
Endpoints
Users
Secrets
Modules
MCP NEW
Scheduled tasks
Database
Tables
Views
Charts
communications New Record
Data Structure
3 rows7 columns Scroll horizontally to inspect every column. Use the row menu to edit or delete.
body created_at updated_at Actions
…ed Your service visit is confir… 2026-06-12 16:50:39.23… 2026-06-12 16:50:39.23…
…ed We will replace the filters d… 2026-06-12 16:50:39.23… 2026-06-12 16:50:39.23…
…ed The service visit was comp… 2026-06-12 16:50:39.23… 2026-06-12 16:50:39.23…
server-side logic · Rust backend

The engine that runs your rules.

Modules, API endpoints, and scheduled jobs. Approvals route to the right person, low-stock thresholds trigger purchase orders, weekly reports send themselves — enforced exactly as the plan says, even at 3am.

Client Service Hub
Specs Preview Settings
Subscribe Publish
…and shared document links. Later versions cover service request submission and broader communication history. Sound right?
Right
Should reminders be sent by email?
not now
v1 v1 released
SpecsAll specs generated
DatabaseSchema created
BackendDeployed
FrontendFrontend deployed
Appointment Knot
Selected as app icon
Make changes, add new features or ask for anything
General
App settings
Domain
Server
Endpoints
Users
Secrets
Modules
MCP NEW
Scheduled tasks
Database
Tables
Views
Charts
Endpoints: 2 Search
customer_dashboard_get
any /customer_dashboard_get
appointment_detail_get
any /appointment_detail_get
built-in authentication

Sign-in that just works.

Email-and-password and Google sign-in, wired in from day one. The roles in your plan decide who can see and do what — you manage access, no security expertise required.

Client Service Hub
Specs Preview Settings
Subscribe Publish
…and shared document links. Later versions cover service request submission and broader communication history. Sound right?
Right
Should reminders be sent by email?
not now
v1 v1 released
SpecsAll specs generated
DatabaseSchema created
BackendDeployed
FrontendFrontend deployed
Appointment Knot
Selected as app icon
Make changes, add new features or ask for anything
General
App settings
Domain
Server
Endpoints
Users
Secrets
Modules
MCP NEW
Scheduled tasks
Database
Tables
Views
Charts
Authorization
Users Providers
Providers: 2
Email
Email and password authentication
Enabled
Configuration
No additional configuration required
Google
Sign in with Google account
Enabled
Configuration
Not configured
encrypted secrets

A safe place for your keys.

Connecting Stripe, email, or a supplier's API means handling secret keys. Yours are stored encrypted in a vault — never pasted into code, never sitting in a spreadsheet.

Client Service Hub
Specs Preview Settings
Subscribe Publish
…and shared document links. Later versions cover service request submission and broader communication history. Sound right?
Right
Should reminders be sent by email?
not now
v1 v1 released
SpecsAll specs generated
DatabaseSchema created
BackendDeployed
FrontendFrontend deployed
Appointment Knot
Selected as app icon
Make changes, add new features or ask for anything
General
App settings
Domain
Server
Endpoints
Users
Secrets
Modules
MCP NEW
Scheduled tasks
Database
Tables
Views
Charts
Secrets: 0 Add Secret Search
KeyValueType
No secrets found
frontend build · Flutter

Screens for your team.

Pages to enter, find, and approve things — built from the workflows and roles in your plan. Runs in the browser, nothing to install. (Building a back-office engine only? You can skip the screens and use it headless — next section.)

Client Service Hub Publish
Appointments
Hello, Yara Doe
Upcoming Appointments
Quarterly Service Visit Upcoming
Jun 17, 2026 • 7:50 PM
123 Main St
Technician arrival window 2:30 PM
Filter Replacement Upcoming
Jun 13, 2026 • 7:50 PM
123 Main St
Replace HVAC filters
Past Appointments
Cancelled Inspection Canceled
Jun 10, 2026 • 7:50 PM
123 Main St
Appointment was canceled by the customer
Hosting Status Publishing
Building… 0:08
This usually takes a minute or two — you can keep working.
Client Service Hub Publish
Appointments
Hello, Yara Doe
Upcoming Appointments
Quarterly Service Visit Upcoming
Jun 17, 2026 • 7:50 PM
123 Main St
Technician arrival window 2:30 PM
Filter Replacement Upcoming
Jun 13, 2026 • 7:50 PM
123 Main St
Replace HVAC filters
Past Appointments
Cancelled Inspection Canceled
Jun 10, 2026 • 7:50 PM
123 Main St
Appointment was canceled by the customer
Hosting Status Live
Add domain
Publish changes
No changes to publish
Last published: Jun 12, 2026 7:55 PM
client-service-h
Appointments
Hello, Yara Doe
Upcoming Appointments
Quarterly Service Visit Upcoming
Jun 17, 2026 • 7:50 PM
123 Main St
Technician arrival window 2:30 PM
Filter Replacement Upcoming
Jun 13, 2026 • 7:50 PM
123 Main St
Replace HVAC filters
Past Appointments
Cancelled Inspection Canceled
Jun 10, 2026 • 7:50 PM
123 Main St
Appointment was canceled by the customer
publishing · building your app

Hosted from day one. Azure

Your app runs on managed infrastructure the moment the build finishes. Nothing to set up, nothing to babysit.

And it's yours. full source export

Export the complete source code anytime and run it anywhere. No lock-in, no hostage situation.

03 · use it anywhere

Use your app from the AI assistant you already have.

Ask questions, pull reports, even trigger workflows from ChatGPT or Claude — no dashboard, no new login. Under the hood, your app exposes an MCP server: the standard that lets AI assistants use software as tools.

Private by default: it is your data in your account, and you choose which services are exposed and what they are allowed to do.
Read the MCP story
real session · a live Metatable app answering from its own data (distributor names changed)
ChatGPT
what are my top distributors?
Looked for available tools
Inventory Operations App · MCP server
→ distributor_performance({ month: "2026-06" })
← 2 distributors · depletions, inventory, velocity

Your top distributors for the selected reporting month (June 2026) are:

Rank Distributor Cases Depleted to Retail Cases Sold to Distributors Depletion Efficiency
1 Metroline Beverage 101.7 cases 189.0 cases 53.8%
2 Garden Grove Spirits 68.1 cases 135.0 cases 50.4%

Additional health metrics:

Metroline Beverage
  • Average weekly depletion: 25.42 cases
  • On-hand inventory: 165 cases
  • Weeks of supply: 6.49
  • Month-over-month velocity change: +2.73%
Garden Grove Spirits
  • Average weekly depletion: 17.02 cases
  • On-hand inventory: 127 cases
  • Weeks of supply: 7.46
  • Month-over-month velocity change: +3.18%

Both grew velocity month-over-month. Want me to break this down by SKU, or schedule it as a weekly report?

Ask anything
ChatGPT can make mistakes. Check important info.

04 · why it holds up

Why it doesn't fall apart at 80%.

Turning a plan into working software is not one prompt. It is a pipeline that builds in the right order, tests against the real thing, and fixes its own errors before you ever see the build.

87%
of backend builds succeeded over the last 90 days — 100% in the last 30.
measured
01

It builds in the right order

Tables before APIs before screens, following the actual dependencies — not whatever the model happens to emit first.

DAG-ordered generation
02

It tests against the real thing

Every query runs on a real database engine and every line of backend code is actually compiled. Errors are found by running the software, not guessed from static analysis.

execution-based validation
03

It fixes its own mistakes

The system reads the real compiler and database errors, corrects its output, and runs it again until the build holds.

self-fixing loops
04

It doesn't lose the plot as your app grows

Each step sees only the relevant part of your plan, so the tenth change is as reliable as the first.

context engineering

05 · honest fit

Built for business software, not every possible app.

When you are ready to compare capacity, see pricing. If you want a fit check first, send us the workflow.

Best fit

CRMs, internal tools, inventory, portals, trackers, approval flows, and operational dashboards.

Use with review

Customer-facing workflows where the data model, permissions, and handoff matter more than visual novelty.

Not best yet

Highly custom consumer interfaces, games, or products where frontend polish is the main product.

Honest limit

Frontend generation is still maturing. The strongest fit today is structured business software.

start here

Have a workflow that should become software?

Describe it, read the plan, and see whether Metatable can turn it into a running application.