The problem: what I can show them Tuesday is a slide
Every sales engineer we talk to describes some version of this — a composite, not a customer quote. They told me the whole returns process on the discovery call: shared inbox, a spreadsheet with eleven tabs, and a warehouse lead who finds out on Friday what came back on Monday. I know what would fix it. What I can show them next Tuesday is a slide.
That is the pre-sales gap. Engineering cannot spare a sprint for a prospect who has not signed. A generic demo calls their Return a Ticket and loses the room. And on a credit-metered builder, every iteration on a throwaway build is a purchasing decision.
What gets built: their nouns, their workflow, a working backend
A working app in the prospect’s vocabulary, before the next meeting. Not a mockup — Postgres tables with a lookup between them, forms with signature and multiple-choice fields, and a workflow that emails the warehouse lead when a return is logged.
- Objects named for their process:
rma_return,rma_item,rma_disposition. Each is a real table with the standard columns underneath. - Forms with the field types the process needs — lookups between return and item, a multiple-choice outcome, a signature on the disposition.
- Workflow that emails the warehouse lead when a return is logged. Their pain point, addressed on the first screen they see.
- Grids for open returns by age and returns awaiting disposition — the two views they said they wished they had.
- Screens generated from the objects; groups so customer service and the warehouse each see their own slice.
Every one of those lines is a named operation on the platform, authenticated with your token. The agent stages the edits, shows you an entity-level diff, and commits when you say so. Nothing is published to the prospect by accident.
Starter prompt
Swap the nouns for the prospect’s own and keep the shape.
Build a solution called Acme Returns for a distributor prospect who tracks product returns in a shared inbox and a spreadsheet.
Objects: Return (customer, order number, reason, received date, status); Item (return, SKU, quantity, condition, photo); Disposition (return, outcome as multiple choice: restock / refurbish / scrap, notes, signature).
Use their vocabulary — it is a Return, not a Ticket, and the outcome is a Disposition.
Create a Warehouse group that sees everything and a Customer Service group that sees Returns and Items but cannot set a Disposition.
Generate the screens, add a grid of open returns sorted by age, and add a workflow that emails the warehouse lead when a Return is created.
Preview the diff before you commit, and do not publish yet — I want to review it with the prospect first.
Ship it: nothing reaches the prospect until you publish
Review the app yourself first — Current is the working copy, and every committed edit bumps its version. One publish and the prospect can click it, not a minute before you say so: publish-solution moves Current to Testing and Production in one step, and the groups you created decide who sees what inside the app.
Iterate after the meeting: add the field they mentioned twice, rename the status they argued about, publish again. No tokens. No credits. No meter. You bring the AI subscription you already pay for. A speculative build costs you the afternoon and nothing else. If the deal closes, the app they saw is the app they get — same data model, no rebuild by engineering.
What the organization license covers, and what it does not: how we price · how the category actually bills, with sources.
Integrations used
Email out of the box. A PDF summary of a return on request, generated by a workflow activity. When the prospect’s ERP needs to know, an ExternalService activity posts to Zapier, Make, n8n or any HTTP endpoint you name.
Related
- For sales engineers — why unmetered matters in pre-sales, and the 24-hour shape of a build.
- Blueprint: CRM-lite — the copyable primitives map for a customer-specific deal app.
- Closed in 24 Hours: Paper inspections replaced in 19 hours — an illustrative pre-sales build, hour by hour.
- Next use case: CRM-lite.
Your IT lead will ask who can publish this, who can see the data, and what the agent is allowed to touch. The answers are written for them: the IT brief · security and governance.