A landing page that converts
Hero, proof, pricing, FAQ and a form that actually posts. Published on your own domain with the certificate issued for you.
app/page.tsx
app/api/signup/route.ts
published · your-domain.com
The screens nobody
had time to build.
Landing pages, internal tools, capture forms, portals, briefs and signable documents — the working software between a spreadsheet and an engineering project.
Seven things people actually ask for.
Each one lists what the run produces.
The tool that never got engineering time
Approval queues, intake forms, field reporting. Real screens for real processes, connected to the system of record.
app/approvals/page.tsx
app/approvals/[id]/page.tsx
workflow · Salesforce update Case
A form that writes into the CRM
Fields, picklists and lookups come from live describe metadata, so the form matches your org rather than a guess.
app/leads/new/page.tsx
POST /workflows/:id/invoke
workflow · Salesforce create Lead
A multi-step flow with real routes
Each step its own route, with a shared progress bar and a draft that survives a reload.
app/apply/company-details/page.tsx
app/apply/documents/page.tsx
app/apply/review/page.tsx
An inbox that reports, not just lists
A Gmail or Outlook search scoped to the mailbox you connect, rendered as whatever view you asked for.
app/brief/page.tsx
workflow · Gmail search_messages
scope · one connected mailbox
A document someone has to sign
Merge app values into a print-ready template, collect a signature on canvas, seal a verifiable PDF.
app/quote/[id]/page.tsx
workflow · Klego Sign sign_document
GET /workflows/sign/:id/verify
No interface at all
One saved workflow with an invocation key, called from a cron job or a service you already run.
POST /workflows/:id/invoke
Authorization: Bearer <key>
every call logged with its input
Who ends up using it.
Usually two people in the same room: the one who knows what it should do, and the one who has to approve it.
Operations
You know the process better than anyone. Describe it; the screen follows.
Sales and revenue teams
Landing pages, capture forms and pipeline views that write into your own Salesforce org.
Engineers
Take the version as a starting point, push it to your own repo, keep going in your editor.
Agencies and consultants
Stand up a concept in front of a client, refine it in the room, hand over source.
It ends on your domain, not ours.
Publish to a public container, point your domain at it, and Klego handles the DNS check and the certificate.