How EchoLogic turns notes and transcripts into a decision record

One decision, followed from a Monday-morning note to the moment it comes back — then the mechanics underneath.

A Real Decision, Start to Finish

Follow one thread through EchoLogic

From a Monday-morning note to months later — every part of EchoLogic it touches, in the order it touches them.
MON · 9:14 AM

A half-formed thought, before it has a home

“Not sure yet if we should raise now or wait for stronger metrics.” Written in the Scratchpad, no whiteboard picked. When the typing pauses, Echo says what it's close to: the runway risk already on Series A Fundraising. File it there and it becomes an open question on that whiteboard.
Not sure yet if we should raise now or wait for stronger metrics.

This is close to a risk on Series A Fundraising.

“Runway assumptions look thin past Q2.” Last week

Open That WhiteboardNot Useful
Speak ItEcho reads when you pause, not as you typeKeep It
MON · MOMENTS LATER

The Continuity Map draws the line on its own

The new question is checked against everything on record. A decision on a different whiteboard already addresses the same risk, so the two whiteboards are now connected — and a third, Mobile Redesign, joins them, because its timeline moved when the pricing test did.
Series A Fundraising
Runway assumptions look thin past Q2.
Resolves →
Pricing Model Experiment
Extend the pricing test 3 weeks.
Related →
Mobile Redesign
Engineering timeline shifted with it.
TUE · 10:40 AM

Talk it through with Echo, on the whiteboard it belongs to

The founder opens Series A Fundraising and asks Echo whether to raise now or wait. Echo answers from what the whiteboard already holds: Monday's question and the runway risk. It's saved there as they talk. When the founder settles on April, after the March numbers, Echo picks it out as a decision, linked to the words it came from, and the founder adds why while it's fresh.
Series A FundraisingAsk EchoOverviewNotesMap
You
Raise now, or wait for stronger metrics?
Echo
This whiteboard has Monday’s question, “Not sure yet if we should raise now or wait for stronger metrics,” and the risk “Runway assumptions look thin past Q2.” Waiting past Q2 means raising with little runway left.
You
Then we raise in April, after the March numbers. Two partners want a full quarter of paid pilots.
Saved to this whiteboard as you talk
On this whiteboard
Decision · picked out by EchoRaise the Series A in April, after the March numbers.“Then we raise in April, after the March numbers.”
Record, added by youWhy · two partners want a full quarter of paid pilotsAlternatives considered · raise now on current metricsRevisit if… · March pilots convert below 30%
Open questionNot sure yet if we should raise now or wait for stronger metrics.Resolved by the decision above
TWO WEEKS IN

Two whiteboards, two different pricing calls — caught before either shipped

On a separate whiteboard, Marketing's pricing test lands on usage-based tiers. Days later Finance locks in flat per-seat pricing for the same segment while building the budget. Contradiction Watch puts both sides next to each other, marked as contradicting, instead of letting either win silently. Finance records the decision that settles it on both whiteboards, and both originals stay on record.
Contradiction Watch
Two decisions on different whiteboards can’t both stand.
Decision2 weeks ago · Contradicts
Move to usage-based pricing for mid-market accounts.
Pricing Model Experiment →
Decision3 days ago · Related
Hold flat, per-seat pricing through Q4 to simplify budget forecasting.
FY Budget Planning →
Record a DecisionOpen Both WhiteboardsNot a Conflict
SAME WEEK

When a decision has too many moving parts for text alone

When text isn't enough, the team lays it out on a Canvas: the timeline switched on, the runway risk connected to the pricing decision with the reasoning on the line, and the term sheet linked to the call it backs.
Fundraising & Roadmap Overview
Illustrative content
Timeline: on
Risk
Runway assumptions look thin past Q2.
Decision
Extend the pricing test another 3 weeks.
File
Pricing-relaunch-brief.pdf
application/pdf · 625 KB
Outcome
Q3 timeline pressure is off.
TWO DAYS LATER

Which tool, and why, kept with the decision

Marketing needs a tool to track the live pricing test. Anyone who can see the whiteboard can ask Tool Advisor. The answer is a tool, a fallback and the reasoning, saved as a decision on that whiteboard and listed with every other tool choice the team has made.
One taskA whole project
File toPricing Model Experiment
tracking the live pricing test
AskAmplitude — saved as a decision on Pricing Model Experiment.
Amplitude for tracking the live pricing test
Today
Pricing Model Experiment · asked by Priya · fallback Mixpanel
THAT FRIDAY

Visible to the departments that need it, private from the ones that don't

The resolved plan is shared with Finance and Marketing — read-only, department-scoped, nothing else on the whiteboard exposed. For anyone outside the company there's a public link to the clean record, set to expire when you choose.
Shared with
EngineeringMarketingFinance
Public link
Turn this private whiteboard into a public EchoLogic page — a clean record of the thinking, not the whole workspace.
echo-logic.ai/share/series-a-fundraising
Copy Link
THE FOLLOWING MONDAY

Finance has a question, and asks it on the whiteboard itself

Read access lets Finance see the plan, not change it, so the question goes on the whiteboard rather than into a thread nobody else will find. The owner keeps it, and from there it's checked against the record like any other thinking — still credited to whoever asked.
Ask on this whiteboard
“Does the bridge change the Q3 budget, or only the runway?”
Asked by FinanceAdd to Whiteboard
A MONTH LATER

A new hire searches “pricing test” — and gets the whole thread

Nothing to dig for: the whiteboard, the Canvas, and the meeting where it was actually discussed all surface at once, scoped to exactly what they're allowed to see.
⌘K
MONTHS IN

By the third round, the pattern gets acted on instead of relitigated

The Continuity Index has now seen this exact tension — simplicity vs. usage-based flexibility — three separate times. It doesn't just log another round; it flags the pattern, so this time the team moves on it instead of re-arguing it from scratch.
Continuity Index
3 weeks in
Decision
Extend the pricing test another 3 weeks.
Recurring pattern
Not enough history yet to spot a pattern.
Continuity Index
4 months in
Decision
Move to usage-based pricing for mid-market accounts.
Recurring pattern
Pricing keeps circling back to the same tension between simplicity and usage-based flexibility — three separate rounds now.
Continuity Index
9 months in
Decision
Lock usage-based pricing as the default for every new mid-market deal.
Recurring pattern
Every prior round eventually landed here. The Index flagged the pattern by round two — this time the team moved on it instead of relitigating it.
Under the Hood

How it actually decides

Four things people ask once they’ve seen the surfaces.
Capture → structured event
1
Read when it's saved to a whiteboard — sorted into decisions, risks, questions, observations and outcomes, not left as plain text.
2
Checked against every event on whiteboards you can already see — related threads link automatically.
3
Every item shows the words it came from. If one is wrong, mark it Not right and it comes off the record.
Contradiction Watch → what “contradicts” actually means
1
Every new event is compared against what's already on record for real overlap, not keyword matching.
2
Matches above a confidence threshold surface as “worth a second look” — never auto-merged, never deleted.
3
You choose: Record a Decision settles it and both originals stay on record; Open Both Whiteboards shows the context; if they don’t really clash, mark it Not a Conflict. The call stays yours.
Tool Advisor → what you get back
1
One tool for the task, a named fallback and the reasoning, saved as a decision on the whiteboard you pick.
2
For a whole project, one tool per task, each saved as its own decision.
3
Every tool decision on whiteboards you can see, in one list.
Department access → how scoping resolves
1
Every whiteboard lives inside one department by default — only its members see it.
2
An Executive role rolls up automatically across every department — no per-whiteboard setup.
3
Sharing is explicit and additive — extending access never changes who owns the whiteboard.
Getting Started

What week one actually looks like

1
Start the trial, name your company, and pick a seat count. That part takes minutes.
2
Executives set up departments to mirror how the org already works, then add the team by email — no individual signups to chase.
3
Start writing the same day — there is nothing to migrate first.
Why Not Just...

Not a wiki. Not a tracker.

A Wiki
Only as current as the last person to edit it. EchoLogic builds its record from how the team already works — nobody has to remember to update anything.
A Tracker
Records status, not reasoning. EchoLogic holds the reasoning behind the status, so revisiting it doesn't mean re-explaining it.
A Continuity Layer
Neither a wiki nor a tracker tells you when two people quietly decided different things. EchoLogic catches it automatically — that's the actual point.
Everything else

Too much to fit in one screenshot.

The rest of what your team gets — all 50 of it, across capture, search, sharing, permissions and the admin work nobody thinks about until it’s missing.
Thinking & record
Inputs
Connection & teams
Platform
Whiteboards
Needs your attention: one ranked feed
Contradiction Watch
Patterns across your whiteboards
Ask Echo on any whiteboard
Meeting summaries
Files read into the index
Documents imported onto a new whiteboard
Whiteboard descriptions
Suggested meaning for links
Blocked items, and who last touched them
Public share links that expire
Team management
Tool Advisor
Notifications
Export or delete your data
Support access only with your consent
Canvases
Continuity Index
Decision records
Watching: what changed since you looked
“Not right” on anything Echo found
Outcomes pulled from meetings
File indexing status
Whiteboard templates
Timeline view on canvas
Team chat on every whiteboard
Cross-department whiteboard sharing
Departments that mirror your org
Company view for Executives
Universal search
Trash with a 30-day restore
Company branding / white-label
In-app bug reporting
Scratchpad: write first, file later
Continuity Map
Decisions worth revisiting
Whiteboard notes
Meeting transcript upload
Meeting commitments to confirm
Files attached to conversations
Topics, sorted for you
Canvas connections
Owners and due dates on open items
Questions on whiteboards you don’t own
Roles and permissions
Decisions captured vs. written up
Weekly digest email
Turn off every public link at once
Seat blocks, self-serve
See it in four situations — fundraising, a pricing conflict, a hiring debate that keeps coming back, and executive oversight.
See Use Cases
Bring your team’s decisions into one continuous record.
From $135 a month for 3 seats · 14-day free trial · See pricing