One note stream per customer, tagged by where it came from

Every note about a person — written on the contact, the pipeline card, the project, an SOP stage or an estimate — lands in one stream, each tagged with its origin.

What it is

A single per-contact note list with a rich-text editor (bold, italic, underline, headings, bullet and numbered lists, preset text colours) and search. Each note carries its origin so a rep can isolate what sales said from what came from the field without losing the one-stream view.

Also called: customer notes · job notes · note history · notes in three different places

See it, piece by piece
01

Notes written on the job, the card, the estimate and the contact land in one stream

Everything anybody has written about a person reads as one list, each note tagged with where it was written. Filter down to just the field notes or just the sales notes when you need to, without giving up the single view. Notes in three places is how the gate code ends up somewhere nobody thinks to look.

Notes
Notes (7)+ Add
AllSOPPipelineEstimateContact
[Field] Zook Barndominium / Framing — Dale Whitmore
Trusses staged on the north side. Owner asked about a third overhead door on the gable end — priced as a change order, waiting on his OK.
Aug 24 at 3:41 PM
[Sales] Contacted — Marcus Feld
Called at 8:40, left a voicemail. He texted back that evening: 40×64, 14 ft sidewalls, budget around $70k, wants it standing before hay season.
Aug 21 at 7:12 PM
[Estimate] SB #990214 — Marcus Feld
Swapped to 29ga painted steel and re-ran the takeoff. New total holds under his number.
Aug 19 at 11:02 AM (edited)
[Contact] — Marcus Feld
Gate code is 4417. Dogs are friendly but loud.
Aug 12 at 9:26 AM
One list carrying [Field], [Sales], [Estimate] and [Contact] notes, with the origin chips above them. The real screen, drawn from the product’s own design system. Sample data — no customer information appears here.
02

A note keeps its origin when somebody opens it on another device

The origin tags used to live only in the browser that wrote them, so the same note read back on a phone came home as a plain ‘Note’ and the categories quietly collapsed. They are stored with the note now, which is the only reason the filters mean anything.

03

Bold, headings, bullets and colour, because a site note is usually a list

The editor handles the formatting a real note needs, and a note that is nothing but a photo still saves. Search highlights matches where they sit in the stream rather than taking you somewhere else.

Notes — add a note
BIUHeading 123
Gate code is 4417. Deliveries go to the second drive — the first one washes out after rain.
CancelSave
The formatting bar with the preset colours that stay readable on the app's ground. The real screen, drawn from the product’s own design system. Sample data — no customer information appears here.
04

Stage moves and system events go to the timeline, not into the customer's thread

The audit history — who moved the deal, exactly when, and which steps were done or skipped — renders on the contact from the same component the pipeline card uses, so the two can never tell different stories about the same job. The message thread stays a record of what was actually said to the customer.

Timeline
Timeline

Same audit history as the pipeline card — every stage move and SOP step, with who and when.

In platform
9d 3h
since Aug 17, 2026
Current stage
1d 18h
Create Estimate
To first contact
7h 36m
created → contacted
New Lead2d 4h
Aug 17, 9:02 AM → Aug 19, 1:15 PM · moved here by Marcus Feld
  • Assign an ownerAug 17, 9:04 AM
  • Make first contact — call, text, or emailAug 17, 4:38 PM
Contacted5d 2h
Aug 19, 1:15 PM → Aug 24, 3:20 PM · moved here by Marcus Feld
  • First contact attemptAug 19, 1:31 PM
  • Follow-up 1Aug 21, 8:40 AM
  • Follow-up 2not completed
  • Add to short-term nurture(optional)not completed
Create Estimate· current1d 18h
Aug 24, 3:20 PM → now · moved here by Dale Whitmore
  • Estimate draftedAug 24, 4:02 PM
  • Verify SmartBuild takeoffopen
  • Confirm markup / priceopen
  • Internal review(optional)open
Time in each stage, the exact moments, who moved it, and the steps left open. The real screen, drawn from the product’s own design system. Sample data — no customer information appears here.
How it works
  1. 1Notes are written with source, source_detail, title and author persisted on the row (migration 202)
  2. 2Origin chips appear only when more than one origin is present
  3. 3Chips filter to Contact / Pipeline / Project / SOP / Estimate / Other
  4. 4Search highlights matches in place; a note that is only a photo still saves
Why we built it

Notes about one person get written from wherever the builder happens to be — the contact, the pipeline card, the project, a stage checklist, the estimate — and the tag saying which one it came from lived only in the browser that wrote it. Open the same note on a phone or a second computer and it came back as a generic "Note", losing the categorisation the stream exists for. Every note now lands in one stream per person with its origin stored alongside it, so it reads the same on any device.

The problem
  • Notes fragmented across surfaces
  • Origin tagging that existed only in one browser's cache
Sound familiar?
What you get
One place to read everything ever written about a customer
Filter to just the field notes or just the sales notes
Categories that follow you between devices

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →