Demonstrations
One demonstration, built properly, rather than a gallery of screenshots
There are no client projects to show, so nothing here is presented as one. What is here is working intake logic you can operate yourself, with its limits written next to it.
DemonstrationLimitation
Available now
RFQ intake, classification and routing
Six prepared requests — including a vague enquiry, a revision of an open job and a message that is not an RFQ at all — run through eleven stages of real deterministic logic.
What it demonstrates
- Classification with a stated rule and the signals that matched it
- Field extraction that records certainty and source per field, and leaves gaps as gaps
- Conflicts between an email body and its attachment, shown side by side
- Duplicate and revision detection against a register of open requests
- A proposed route with the full rule evaluation behind it
- A human review step that actually changes the output and the audit trail
What it does not prove
- Extraction accuracy on arbitrary real-world documents
- Any production accuracy figure
- Compatibility with your ERP or quoting system
- Any ability to read technical drawings
- Any ability to calculate a price
- Reliability at volume, over time, in production
Not yet built
What would come next
Listed as intent, not as a roadmap commitment, and not as pages that exist somewhere else on this site.
- A quote follow-up demonstration showing the approval queue and stop conditions
- An order-entry demonstration showing idempotent writes and difference reports against a quote
- A shared-inbox triage demonstration with confidence thresholds and a review queue
Request a workflow review
Your intake is messier than the demonstration
It always is — real inboxes contain forwarded threads, phone notes and portals that email nothing useful. The review is where that mess gets described honestly, before anyone proposes building anything.
30-minute review. You receive a concise written recap. No obligation.
Engagement capacity is intentionally limited so discovery, implementation and handover remain founder-led.
Prefer to read how it is built? The teardown covers architecture, state transitions, failure modes and the security boundary.