Case study

Meet Penny: AI that drafts and checks while the adviser decides

Penny House, a mortgage brokerage, had AI work spread across Claude skills, ChatGPT scheduled tasks and a lead-control app, with no system owning the case. We are building Meet Penny: a control layer that gives every case an owner, next action and deadline, with AI drafting and checking inside it and advice left to the adviser.

2026–today

What we built

  • One canonical record for every lead and case
  • Owner, next action and deadline on every case
  • Adviser approval packs at each regulated gate
  • Administrator work queue with scripts and evidence
  • AI document intake with sources and confidence
  • Audit log and visible exception queue

The challenge

Penny House had already put AI to work. Claude skills read client documents, checked case files and drafted case paperwork; ChatGPT scheduled tasks watched the inbox, sent reminders and produced reports; a lead-control app had been built in Lovable. But the adviser was still the integration layer. Information moved between email, case files, the CRM, sourcing tools, lender portals, spreadsheets and AI projects by re-keying, and no tool owned the case: its stage, owner, next action, deadline or approval history. Case progression, the stage that takes the most admin time, had no tool at all, and every change had to respect the controls of the principal firm the brokerage advises under.

What we did

  1. Handover — the brokerage's Claude skills, ChatGPT scheduled tasks, lead-control app and compliance checklists, mapped against a single case lifecycle from first enquiry to renewal
  2. Phase 0, discovery and controls — demonstrate every existing skill, schedule and app, and agree with the adviser and the principal firm what the system may read, draft, write, send, move, delete and submit
  3. Phase 1, control layer — one lead, case and task model with unique IDs, an owner, next action and deadline on every case, an audit log and an exception queue
  4. Phase 2, intake and file control — match email to cases, create case folders from the file model, and run the existing document intake and file checks as orchestrated modules
  5. Phase 3, routine-case pilots — product transfers and straightforward remortgages run by the administrator, reaching the adviser only at defined gates with complete evidence

What we built

The design rests on one rule. If a job needs durable state, timing, permissions, integration, retry, audit or a guaranteed outcome, it belongs in software. If it interprets unstructured evidence or drafts language, AI can assist. If it is regulated judgement or final accountability, it stays human.

So the workflow engine, not the model, decides when AI runs, what it may touch and where its output goes. Each run gets a bounded task, an approved snapshot of the facts and an output schema, and returns its evidence, confidence and exceptions. The adviser makes every recommendation and signs off every suitability letter, and a person always clicks Submit on a lender portal.

The brokerage's method moves out of chat prompts into a version-controlled library, so Claude and ChatGPT become replaceable workers, shadow-tested against each other before either becomes the default for a task.

Screen 1 Adviser dashboard: approvals and exceptions
Screen 2 Administrator work queue

The result

Meet Penny is in build, control first. The first goal is that every new enquiry and pilot case is visible, owned and auditable. Each workflow then starts in shadow mode, with AI proposing while a person acts, and moves through testing, the adviser's approval, limited production and monitored scale, with a rollback and a manual fallback. Success is measured as revenue per adviser hour, alongside time saved, re-keying removed and approval exceptions.

Stack
  • Claude
  • ChatGPT
  • Microsoft 365

Got something similar?

Tell us what is slow, manual or held together with spreadsheets. Or call 0333 444 2298.

Book a free consult