Now in private beta
Independent consultants · small agencies

Calls in. Branded deliverables out.

CallCraft turns client call transcripts into a matched set of polished deliverables — meeting recap, SOW, proposal, and follow-up email — styled with your firm's colors, fonts, voice, and pricing logic. Hours of post-call work becomes minutes.

CallCraft's before · after

CallCraft's transcript, recharted for a client packet.

Same call, same minutes. The raw export on the left, the matched packet CallCraft actually ships on the right — placeholder data, real chrome.

Acme-CallCraft-discovery.txt — placeholder
Sample copy
Sample placeholder transcript

Acme / CallCraft discovery

Raw notetaker export — no formatting, owners lost in the rambling.

[Sample placeholder transcript — Acme / CallCraft discovery]
[00:01] Lila (lila@acme.co):  Okay so today we are going to talk about the integration with... um... well let me think about where we are.
[00:42] Lila:  So basically we want help with the onboarding flow, and there is also the audit, but also there are some other things too.
[01:30] Host:  Got it. Before we touch that — what is the timeline?
[02:08] Lila:  Soon-ish, ideally Q2. Our finance team is asking for a number but I do not know the exact... they will need to sign off.
[03:14] Host:  Okay so phase one would land in Q2. Should we scope that as audit plus two sprints?
[03:47] Lila:  Yeah that sounds right. Also we may want a third sprint later but not decided yet.
[05:01] Host:  I will put the proposal together once the recap lands.

no owner pulled from the transcript · no follow-up queued · no branded letterhead

Meeting recap

CallCraft · on-brand letterhead

Sample preview

Acme / CallCraft discovery

Phase one ships in Q2. A third sprint is held for a later Q3 conversation, and Acme finance still has to sign off on phase-one pricing before the proposal locks.

  • Lila (Acme) — sends the audit scope by Mar 18 so CallCraft can scope phase one against the real inputs.
  • Maya (CallCraft) — drafts the proposal once this recap lands.
  • Devon (Acme finance) — signs off on phase-one pricing.
Statement of work

CallCraft · on-brand letterhead

Sample preview

Statement of work

**Effective Mar 17 · 6 deliverables · $24,000 fixed.**

  • Audit of the Acme onboarding flow (3 business days).
  • Two implementation sprints, billed weekly.
  • UETA-aware signature flow on the share link.
  • Weekly status recap on Friday end-of-day.
  • Final hand-off doc + Loom walkthrough.
  • 30-day post-launch support window.
Client signs via the share link · CallCraft countersigns the same hour.
Proposal

CallCraft · on-brand letterhead

Sample preview

Proposal — Acme × CallCraft

TierScopeTimelineInvestment
Phase oneAudit + two sprintsQ2 (8 weeks)$24,000
Phase twoThird sprint + onboardingQ3 (4 weeks)$14,000
RetainerPost-launch support30 days$3,000 / mo

Pick the phase-one path to start. Phase two and the retainer kick in only if Acme wants to extend past the hand-off.

Share + sign link

CallCraft · on-brand letterhead

Sample preview

Share + sign

/share/c8e4f9a2-7b1d-4f6e-9a3b-8d2c5e1f4a7b

  • Acme opens the link — reads the SOW, proposal, and recap in one packet.
  • Signs via the e-sign surface — UETA / ESIGN aware, audit trail attached.
  • CallCraft countersigns the same hour; the row flips to ready.
Legal-grade binding without the back-and-forth.
Works withOtterFathomFirefliesRead.aiTactiqAny notetaker

How it works

From transcript to client-ready in three steps.

The same three a new trial user sees in the onboarding checklist and the welcome email — upload, extract, ship.

Step 01

Upload or paste your call transcript

Drop in the raw transcript — Otter, Fathom, Fireflies, plain text, .vtt. CallCraft reads the room.

Step 02

CallCraft extracts the matched-set context

Decisions, next steps, blockers, follow-ups, owners, dates — pulled from how the call actually went, not how a template presumes.

Step 03

Generate your branded deliverable

One click ships the recap, SOW, proposal, and follow-up email — on your letterhead, in your voice, in minutes.

What customers say

Three independent consultants · one shared workflow.

CallCraft ships to solo firms the way a platform would, at the price of a tool.

JR
Jamie R.Independent consultant

I went from 90 minutes of post-call work to 12. CallCraft’s recap + SOW arrived before I closed my notebook.

PN
Priya N.Acme

Three deliverables, one transcript, my letterhead. My clients stopped asking which doc was the source of truth.

MD
Marco D.Small studio

The proposal ladder alone earns the subscription. I stopped reinventing tier tables every Monday morning.

The product, one scroll

What you ship, how it works, and what it looks like.

Four matched deliverables from one transcript, on your letterhead. Below: the outputs, where CallCraft sits in your stack, and three anonymized samples you can switch between.

What you ship

For a check-in call
Branded meeting recap
Decisions captured, action items assigned, owners named. Sent the same hour the call ends.
For a discovery call
Statement of work
ESIGN / UETA aware, ready for signature. Scope, timeline, payment — already aligned to your pricing.
For a scoping conversation
Proposal draft
Three-tier pricing ladder built from the inputs. Structured, distinct, defensible.
For every call
Follow-up email
Short, on-tone, on-brand. Replaces the loose "thanks for your time" paragraph you send at 11pm.

Where CallCraft fits

Keep the notetaker your team already uses. Keep PandaDoc or Qwilr for signature. CallCraft sits in the middle and turns the raw transcript into on-brand deliverables ready to ship.

Upstream · already on your desk

Otter
Fathom
Fireflies
Read.ai
Tactiq
Any notetaker

Downstream · export targets

PandaDoc
Qwilr
Google Docs
PDF
Markdown
Email-ready HTML
Three anonymized deliverables

Switch between the three artifacts — same letterhead.

Each panel is a polished deliverable rendered through the same engine CallCraft ships for signed-in consultants — recap, SOW, and proposal — with letterhead and pricing terms the client can sign the same hour.

Meeting recap

Northwind Logistics — onboarding refresh kickoff

CallCraft · on-brand with the CallCraft letterhead

Sample preview

Prepared by CallCraft

CallCraft logo CallCraft · Meeting recap — Northwind Logistics onboarding refresh · kickoff check-in · 14 Aug 2026

Northwind Logistics and CallCraft agreed to anchor the onboarding refresh on a four-week build, with three milestones kept explicit so the client can hold the work without rerunning the discovery thread.

Northwind's internal pilot deadline lands 30 Sep 2026, which forces a hard cut on any scope that has not started by the end of week two; north-of-scope work will be quoted under a separate change order rather than absorbed into the base engagement.

TL;DR

  • Phase one ships as a four-week single-team build (audit, two sprints, retro).
  • Northwind logistics ops owns field rollout; the Northwind IT lead owns the auth cutover.
  • A separate procurement week is held off the main schedule and gated on Northwind finance sign-off in week three.

Phase one ships in Q3 as a four-week build. A procurement week is held off the main schedule and gated on Northwind finance sign-off — anything past that window moves to a separate change order.

Key decisions

  • Decision: Phase one is a four-week single-team build, not a phased cross-team rollout. — Decided by Priya (Northwind ops) and corroborated by Devon (CallCraft).
  • Decision: The auth cutover ships inside phase one rather than a separate phase. — Decided by Marcus (Northwind IT) with Devon (CallCraft) signing off on the integration risk.
  • Decision: Northwind field training is held until the pilot is complete. — Decided by Priya (Northwind ops) after weighing the pilot deadline.
  • Decision: Procurement scoping is gated on Northwind finance sign-off in week three. — Decided by Devon (CallCraft) and accepted by Priya (Northwind ops).

Action items

#OwnerActionDue
1Marcus (Northwind IT)Send SSO metadata and the list of identity-claim mappings CallCraft needs for the integration spike.Tue 19 Aug
2Priya (Northwind ops)Name the two pilot sites and confirm the field lead for each.Wed 20 Aug
3Devon (CallCraft)Run the architecture spike against the SSO metadata and write up either a fit/fix or a second-pass integration.Fri 22 Aug
4Devon (CallCraft)Draft the SOW draft reflecting the four-week build and route it to Priya for redlines.Mon 25 Aug
5Devon (CallCraft)Hold a procurement scoping-quote line-item for Northwind finance sign-off in week three.Open; gated on finance sign-off in week three
6Priya (Northwind ops)Schedule a 30-minute check-in once the SSO spike lands.After #3

Discussion highlights

SSO and identity integration

Northwind IT is migrating from a legacy SSO into a modern identity provider and the integration risk sits in the claim-mapping middle. Marcus confirmed the migration is mid-flight, so the spike is the spec-driving input rather than a parallel track. CallCraft will scope the integration against the spike output rather than the legacy auth contract.

Pilot scope and field rollout

Priya confirmed two pilot sites for the phase-one test, with field training intentionally slotted after pilot completion rather than during the four-week build. That schedule protects Northwind from a rollout race with the pilot itself and gives CallCraft a clean retro window with the field leads.

Procurement hand-off

Northwind finance has to sign off on the procurement scoping before the quote is firm. Devon honoured that gating in the SOW draft — the quote line-item sits open until the week-three finance sign-off, then closes inside the same engagement so the Northwind procurement hand-off stays inside the CallCraft single-team envelope.

Risk on the auth cutover

The SSO metadata may not arrive clean. Marcus accepted the risk of a second-pass integration at the Cost of a longer week-two spike, so the SOW draft reserves an explicit contingency in week two rather than collapsing the timeline.

Open questions

  • Will Northwind IT standardise the SSO claim-mapping in time for the spike, or do we plan for two mapping iterations?
  • Does Northwind Ops want the field lead copied on the weekly status note, or do we hold that report inside Northwind ops leadership?
  • Is the procurement scoping expected to land inside the same engagement envelope, or do we cut a sub-engagement letter for that week?

Next step

Devon sends the SOW draft by Mon 25 Aug with the four-week build, the auth cutover inside phase one, and an open procurement line-item guarded by week-three finance sign-off.

— CallCraft

Meeting recap — sent within an hour of a check-in. Captures decisions, owners, and due dates the client can act on without rewinding the recording.

~5 minFrom call end to client packet
4 outputsMatched deliverables per transcript
$10 → $20Per-seat · billed monthly, cancel any time
ZeroWhisper + LLM + proposal suite to stitch

Pricing

Per-seat subscription, designed to undercut.

Per-seat monthly subscription in two tiers. One subscription replaces the stack of tools you'd otherwise stitch together.

Solo

$10 / seat / month
For the independent consultant turning weekly client calls into deliverables.
  • All four branded deliverable generators
  • Custom brand profile (logo + colors) on every output
  • PDF and markdown export on deliverables
  • Deliverable history
Most popular

Pro

$20 / seat / month
For consultants shipping more packets each week, who want them summarized and out the door.
  • Everything in Solo
  • Higher monthly generation/usage limit than Solo
  • Weekly digest email of generated deliverables
  • E-signature on shared SOW/proposal links

Frequently asked

Questions, before the call.

If you're evaluating CallCraft, send us a note — we read every one.

CallCraft works from the transcript — plain text, .vtt, or any notetaker export. Otter, Fathom, Fireflies are first-class; anything else still works because it just reads the room.

Now in private beta

Stop stitching. Start shipping.

Send us a recent transcript and we'll send back a sample packet — on your colors, in your voice, in under a day.

Read by a human. Replied to in one business day.