Acculabs — Post-Discovery Brief

Snapshot

Company

Acculabs · Chicago

Specialty chemicals for metal plating & surface finishing. ~15 people, 200 clients, 400 products, 1,000 proprietary formulas. Owner-operator acquisition 2024 (Luca).

Temperature

Warm · Slow timing

Q3 objectives already set — repricing not top-3. Open to exploring Q4. Next: send a concept note + NDA to plant the seed.

Hypothesis check

A2 Quote Gen — Wrong

"Non facciamo miliardi di proposte." Low quote volume, simple enough to handle. The real pain is upstream: keeping 200 custom price books current.

Agreed next step

Pensierino + NDA

Raffaello to send a brief concept note on how repricing automation could work. No proposal yet. Start the NDA conversation to unlock the pricing data.

Confirmed pains · from transcript

Repricing — custom price book maintenance

≈ 150–200 hrs/yr · CEO time

All 200 clients have fully custom pricing. No standard price list. Luca manually reviews every incoming order — checks when the price was last updated, inflation, raw material movement — then makes a judgment call. He estimates 3–5 hrs/week.

01
Map order → client → product — partially automatable. Email arrives, link to customer, link to products in the order.
02
Calculate adjustment — deterministic. How long since last price increase? What moved in raw materials/inflation?
03
Judgment call on timing — human-in-loop. Is now the right moment to raise? Draft notification to client.

"Fai conto che questo è un esercizio da tre o cinque ore a settimana per me... centocinquanta, duecento ore" — Luca

IP constraint: Formulas cannot leave their network. Rules out standard OpenAI/Claude API. Would need a local model or Azure/OpenAI with zero-retention contract.

Product knowledge capture

Low urgency

1,000 proprietary formulas + application know-how (which product for which metal, temperatures, troubleshooting) live entirely in 2–3 people's heads. Discussed voice-capture agent or structured interview sessions → Airtable. Not a Q3 pain, but Luca is aware of the key-person risk.

Lab reports & order entry

Closed — building internally

Not an opening. They're already automating this themselves.

Key reflection for Giuseppe

Is repricing adjacent enough to quoting to add to our module registry — and is this pain common enough to build a customer base around?

Quoting vs. repricing — side by side

Quoting · Module A2 · what we built

Trigger

Incoming RFQ from customer

Input

Customer request + product specs

Output

Price quote for a new order

Knowledge required

Product catalog + spec matching

ERP data touched

Price tables + product master

Mode

Reactive — triggered by customer

Repricing · new territory

Trigger

Incoming order from existing client

Input

Price history + cost indices + time elapsed

Output

Updated price book + client notification

Knowledge required

Cost data only — no product formulas

ERP data touched

Same price tables · same connector

Mode

Proactive — triggered internally

🟡

Adjacent, but a distinct module. They share the ERP connector and the determinism + judgment blend. But the trigger, knowledge domain, and output are different. This is not an A2 extension — it would be a new entry (A2b "Price Book Intelligence"), potentially deployed together with A2 as a Track A price intelligence package.

✅

One meaningful upside. A repricing module makes A2 quoting more accurate — you're quoting from a clean, current price book. The two compound each other. If we add repricing, it's not a silo; it strengthens the overall Track A story.

Is this pain common enough?

ICP for repricing

B2B specialty manufacturer or distributor with fully custom pricing per client — not a standard price list with discounts. 10–50 people, no pricing analyst, no enterprise CPQ tool.

Why Acculabs is the peak case

All three pain conditions simultaneously: custom pricing + small team + IP constraint on cloud. The pain is real, quantified, and CEO-owned. Ideal design-partner profile.

The market gap

Enterprise CPQ tools (Vendavo, Pricefx) start at $30–100K/yr — too expensive for this size. Many companies in the 10–50 person band just absorb the manual hours or rely on a spreadsheet.

The concern

Companies with standard price lists + client-level discounts won't have this problem. The target is narrower than quoting pain — only companies where every price is negotiated individually. Worth qualifying early.

⚖️

Medium replicability. The pain exists in specialty chemicals, industrial distribution, professional services, custom manufacturing. But it's narrower than quoting volume pain. Suggested action: add "custom vs. standard pricing" to the ICP checklist — one question at discovery that filters fast and tells us how often this comes up in the pipeline.

Timing

Now — send pensierino + NDA. A short concept note on how the repricing automation would work. Low-risk: it's a concept, not a proposal. Plants the seed, opens the NDA conversation, and shows momentum without asking for a commitment from Luca.

Q3 (Jul–Sep) — low friction. Luca is heads-down on Q3 goals. Don't push for a call. One check-in message in September is enough.

Q4 (Oct+) — natural re-entry. If we've built or scoped a repricing module by then, Acculabs is the obvious first pilot candidate. Come back with something concrete rather than a concept.

Decisions for Giuseppe

Is repricing adjacent enough to add to our module registry?

Proposed entry: A2b "Price Book Intelligence." Shares the ERP connector with A2, different trigger + output. If yes → add to module-registry.md, include in future pre-proposals when discovery surfaces custom-pricing pain.

Is Acculabs the right first customer, or should we find a stronger urgency fit first?

Acculabs is the peak ICP match for this pain but the timing is Q4 at best. If another pipeline company surfaces the same repricing pain with faster urgency, we might learn and build faster elsewhere — then bring Luca a working demo instead of a concept.

Send the pensierino now, or wait for Q4?

Raffaello's instinct from the call: send soon. A concept note is low-stakes, keeps us visible, and starts the NDA process early. Waiting risks going cold. The risk of sending too early is minimal — Luca explicitly said he's open to exploring it.

Add "custom vs. standard pricing" to the ICP qualification checklist?

If repricing becomes a module, we need to know from discovery whether a prospect has fully custom per-client pricing. One question costs nothing and starts building signal on how common this pain is across the pipeline.