CUSTOMER ACCOUNT / ATTRIBUTED EVIDENCE
What this case establishes
This is a commercial publisher’s customer account. Roseram checked the source and wrote the analysis; it did not interview the customer, run the product, audit the figures or establish that AI caused the reported business result. The pilot below is a proposal, not a completed experiment.
Primary material reviewed 2026-10-12. Analysis and proposed evaluation by Roseram Editorial.- 01Redacted discovery context
- 02Task-specific prototype
- 03Feasibility and prospect review
Proaction: the documented workflow
OpenAI describes Proaction cofounder Colin Knudsen using Codex and prospect context to build custom HTML demonstrations. Its September 2026 account reports four to six demos a month, typically prepared in 30–45 minutes. A reported increase in deals progressing through a sales stage is not the same measure as booked revenue, and Roseram did not audit the figures.
The mechanism worth examining
A discovery call contains the language of the prospect’s problem: which vehicle needs attention, which spreadsheet is trusted and which handoff fails. Turning that into a screen helps test whether the proposed workflow makes sense. AI coding is useful when it connects a specific question to an inspectable interaction, rather than producing a generic dashboard with attractive but meaningless charts.
The implementation decision
Use synthetic fleet records and identify one decision the prospect needs to make. State which data and controls are illustrative. Keep the prototype separate from production accounts and do not imply that a generated screen is an already shipped integration. A sales engineer or product owner should review feasibility before the demonstration becomes a contractual commitment.
Where the workflow can fail
A convincing demo can suggest features that the product cannot safely deliver. Discovery notes can contain confidential information unrelated to the task. Generated forms may also appear to save data while only changing local state. Label mocked behavior, minimize the supplied context and test what each visible action actually does. A prospect should understand where the concept ends and current functionality begins.
A practical evaluation, designed for this use case
Test the demo against the discovery question, not against visual polish alone. Can the prospect locate the relevant vehicle, understand the proposed next step and explain what would change? Measure preparation and correction time, then track the defined sales-stage outcome separately. A later production implementation needs its own permission, data and reliability review.
Primary sources
Figures and product details above are dated and attributed; they are not current guarantees.
- OpenAI: Proaction primary account ↗The attributed workflow and reported result. Proposed pilots and decisions below are original Roseram analysis.
The decision matrix
Original evaluation criteria for this workflow. These are questions to test, not results measured by Roseram.
| Decision | Evidence to collect | Stop or revise when |
|---|---|---|
| Relevance | One prospect task represented | The demo is a generic feature tour |
| Honesty | Mocked behavior clearly identified | A concept is presented as a shipped feature |
| Measurement | Sales-stage definition retained | Pipeline progression becomes a revenue claim |
YOUR EVALUATION / NOT A REPORTED RESULT
A small pilot you can inspect
Use these steps as a planning checklist. Checking a box records your progress in this view; it does not run or validate an experiment.
Questions this case answers
Is a tailored demo a production application?
No. A prototype can validate understanding without establishing production readiness.
Does sales-stage progression prove higher revenue?
No. Stage movement and realized revenue need separate records and definitions.
Tools & capabilities referenced
Operators studying this story often evaluate adjacent AI products. Explore Roseram guides where available:
PRACTICAL NEXT STEPS
Take the evidence into your own project.
Calculate the whole project cost
Compare subscriptions, usage, launch work and renewals.
Test an existing-project workflow
Check import, source loading, preview and publication.
Verify the output you buy
Require evidence tied to a real customer task.
Wiki brief
Proaction is examined here for prospect-specific software demonstrations. The article answers “How can AI coding turn discovery calls into useful product demos?” using linked primary material and original evaluation design. It is not a customer testimonial for Roseram or an endorsement by Proaction.
Operator takeaways
- Demonstrate a decision.
- Label mocked behavior.
- Measure the actual sales stage.
Related case studies
Plan → build → review with routed models and transparent usage.