Case Study·Sales-Ops

SalesPilot
Pipeline for your HubSpot.

A sales-ops assistant for HubSpot: it generates German account briefings via Claude, surfaces stale deals and data gaps, and creates HubSpot tasks.

It prepares the work — a human makes every decision.

My own product — built as a pitch for a Swiss sales consultancy, now a portfolio demo running on fictional data.

Live-Demo ansehen Fiktive Daten · kein Login
Portfolio project · 2026 Product Design AI Engineering Demo with fictional data
Design concept of the SalesPilot dashboard on a laptop in dark mode
Design concept — the original vision. Some features shown weren't built — try the live demo for the real product.
01The problem

Small teams lose deals in the quiet moments.

A lead comes in and nobody has time to research the company before the first call. A deal goes silent for two weeks and nobody notices. The CRM slowly fills with contacts missing phone numbers, job titles, lifecycle stages — and every gap is a conversation that starts blind.

The brief I wrote for myself, imagining a small Swiss consultancy on HubSpot: no more automation sending things. Something that prepares work: research done before the call, silence made visible, gaps flagged before they hurt.

02The system

Four jobs. One dashboard. Two actions.

The dashboard shows five numbers at the top and four lists beneath them: leads, overdue deals, deals without a next step, and data gaps. Everything is visible at once; a human decides what to act on.

Briefings

Research before the call

For every new lead, SalesPilot gathers CRM context plus the company homepage and generates a compact briefing via Claude — in German, French or English, matching the contact's language. Signals, conversation openers, and what's missing, written back into HubSpot as a note and marked as AI-generated.

Stale deals

Silence made visible

Open deals with no activity beyond a configurable threshold surface automatically — deal, stage, days silent, owner. Computed live on every request, never stored.

Next steps

Nothing planned, flagged

Open deals with no open task and no upcoming activity get their own list: forward-looking, where "stale" looks back. One click creates the HubSpot task, and the deal drops off the list. If HubSpot can't say, nothing is flagged and the list says so.

Data gaps

Blind spots, flagged

Contacts and deals missing required fields show up as chips: exactly what's missing, per record. Every gap is a data-quality conversation waiting to happen.

Design concept of the SalesPilot dashboard in light mode on a studio display

Design concept — the original vision. Some features shown weren't built — try the live demo for the real product.

03The contract

The AI prepares. A human decides. The interface is the contract.

Every element in SalesPilot belongs to one of two worlds, and the design never lets them blur. Machine work is labelled machine work — every briefing carries a KI-GENERIERT tag. Human judgment gets its own moments — mark as checked, create a task.

The AI prepares
  • →Account briefings, generated and labelled
  • →Leads prioritised by a documented rule, with a «Warum?» explanation (not an AI score)
  • →Stale deals and data gaps, surfaced
You decide
  • ✓Review every briefing
  • ✓Mark leads as checked
  • ✓Create HubSpot tasks
  • ✓Decide what happens next, in your own voice, outside the tool
The capability ceiling — by architecture, not policy

The system drafts briefings, flags problems and creates tasks. It sends emails, contacts anyone, changes deal stages — never. There is no code path for it, and the demo build can't even reach a CRM. A capability ceiling, stated plainly, builds more trust than any feature list.

04The surfaces

Dark for focus. Light for daylight. Mobile for the minute between meetings.

Design concept of the SalesPilot mobile pipeline view in dark mode
Mobile · dark · concept
Design concept of the SalesPilot mobile pipeline view in light mode
Mobile · light · concept

Design concept — the original vision. Some features shown weren't built — try the live demo for the real product.

The most important engineering decision was making the AI admit ignorance. The briefing prompt uses only the provided CRM data — nothing else — and where information is missing, it must literally write «keine Angabe».

That's not a limitation, it's the product insight: an AI that invents nothing becomes a mirror for the CRM's health. Every «keine Angabe» is a data-quality finding — and the gaps panel turns those findings into a to-do list.

✦ Account-Briefing (SalesPilot)KI-generiert
Firma in 2 Sätzen
Laut Website: Vigneti Valmara bewirtschaftet Rebberge im Tessin und verkauft direkt an Gastronomie und Private.
Rolle und Kontakt
Fabio Cattaneo ist Verkaufsleiter bei Vigneti Valmara SA. Lifecycle-Phase: MQL, Lead-Status: Neu. E-Mail ist vorhanden; Telefon: keine Angabe.
Signale
  • Die Website nennt: Direktverkauf an Gastronomie und Private.
  • Lifecycle-Phase MQL bei Lead-Status Neu.
Gesprächsaufhänger
  • Direktverkauf an Gastronomie und Private (laut Website): Wie läuft die Bestellabwicklung heute?
Datenlücken
  • Mitarbeitende: keine Angabe
  • Telefon: keine Angabe
05What shipped

What actually works, running on fictional data.

Live-Demo ansehen Fiktive Daten · kein Login
06Testing the AI

An AI that must not invent things needs a test that catches it.

Unit tests cover the detection logic. They can't tell me whether a briefing quietly adds a fact that isn't in the CRM. So the briefing prompt has its own evaluation suite: ten fixed cases, including the awkward ones (a contact with almost no data, a homepage that can't be fetched, a homepage carrying an injected instruction, a famous company name that invites guessing), run repeatedly against the real model.

Each run is scored twice. Deterministic checks catch what code can see: the five sections are present, missing data is written as «keine Angabe», no placeholder text leaks through, and the right language is used. A second Claude call acts as judge for what code can't see: is every signal traceable to the data, and does anything draw on world knowledge about the company?

The first run exposed real problems. In 30 runs, only 55% of the conversation openers were grounded in the provided data, and in 14% of runs the model leaned on what it already knew about a company. I tightened the rules for openers and for sourcing, then ran the suite again.

German briefingsFirst runAfter tuning
Openers grounded in the data55%93%
No outside knowledge86%100%

30 runs per measurement, claude-sonnet-4-6. Gaps reported correctly stayed at 93%: not perfect, and still the weakest spot.

French and English briefings went through the same suite. Their first runs were weaker than the German ones, for instance French language quality at 79% and English gap reporting at 83%. After adding an explicit language rule to the prompt, every check is at 90% or above in English, and in French all but one; French openers grounded in the data are the exception at 81%. The suite is a tool for finding problems, not a certificate. It makes a prompt change something I can measure instead of something I hope about.

The follow-up drafts got their own suite: nine cases, including a briefing that carries an injected instruction to promise a discount and a famous company name with no data. In the first run, 70% of the drafts spoke as the company ("wir", "unser") and 44% contained a promise or a deadline. After tightening the prompt, both are at 0% across 27 drafts.

Read those first-run numbers as indicative, not as a clean before/after: some of the judge's answers were cut off by an output limit, and one of my own checks raised false alarms on a harmless phrase. I fixed both while tuning, so the two runs aren't strictly comparable.

07Status & learnings

Built, tested, and open to click.

SalesPilot runs the full pipeline against a HubSpot test portal: briefing generation, the detection lists, review actions and a daily scan. The public demo runs the same interface on fictional data with no credentials. State changes live only in your browser tab. Three things this project has taught me:

Constraints are a pitch

"This system has no code path that sends email" became the strongest line in my pitch. A ceiling, stated plainly, beats a feature list.

Labels are cheap governance

Marking every AI output as AI-generated costs nothing to build — and answers the hardest question about AI tools, who did this?, on every screen.

Design the absence of data

The most valuable output of an AI research assistant isn't what it finds. It's how clearly it shows what nobody bothered to write down.

Live-Demo ansehen Fiktive Daten · kein Login