01
Counsel
We sit with the people doing the job and decide what’s worth building. Strategy that ends in a system — not a deck that gathers dust.
Partner newsSymboli named to Perplexity Computer’s founding partner cohortImplementation partners · 2026Talk with us
Counsel · Software · Implementation
Advice that ships.
Most consultants hand you a recommendation. We hand you working software — then stay until your team reaches for it without being asked.
engagement-plan.md
How every engagement runsEvery engagement runs all four. Most firms stop after the second row.
What each phase produces
Four phases. Four things you can actually hold.
Nothing here is slideware. Notes taken on your floor, a memo you signed, code in your repo, and evidence people actually use it.
01 · Sit
We start on your floor, not in a workshop
A questionnaire tells you what people think they do. We watch the actual day — the tabs, the waits, the workarounds nobody wrote down — and take notes as it happens. You get those notes, and the pattern sitting underneath them.
field-notes.mdrecording
On site · a normal week
What we watched
- 09:12Same question asked in three places before anyone answers.
- 09:31Two people rebuilding the same weekly summary.
- 10:04Approvals wait on one person’s inbox.
The pattern underneath
The answer already exists. Finding it is the job.
Written on your floor, not in a workshop
02 · Decide
Most of what we find shouldn’t be built
Software is the expensive answer, so it has to earn it. Every observation gets a call — leave it alone, change a rule, or build it — and you sign off on that memo before anyone writes a line of code.
decision-memo.pdfin review
Straight from the field notes
What we do about it
- The weekly status ritualPeople rely on it and it worksKeep
- Approval routingA rule change beats a new toolChange
- One place for the answerCited from systems you already runBuild
- A named owner and a ship dateAgreed before any work startsCommit
Signed before any code
Your team
Symboli
One build. One rule change. One thing left alone.
03 · Build
The people who advised you write the code
Nothing gets thrown over a wall to an implementation partner. The same team that sat with you builds it, reviews it, and merges it into the tools your team already opens every morning.
symboli/answer-deskopen
#128
Add cited answer surface
The one thing the memo said to build
lib/answer.ts
-// TODO: ask ops for the latest policy doc
+const docs = await search(q, { scope: "org" });
+return cite(summarize(docs), docs);
+export const runtime = "nodejs";
- typecheck0 errors
- tests24 passed
- previewdeployed
Shipped
Merged into the workflow your team already uses
Written by the same people who took the brief
04 · Stick
Launch day is where most projects quietly die
A tool nobody opens is the same as no tool. We watch how it actually gets used and stay through the awkward middle — until reaching for it is the habit, not the thing someone has to remind the team about.
adoption-reportafter launch
Use over time
It climbs, or we are not finished
Share of the team using it, week by week
launchlater
What we watch for
- People reach for it without being asked
- The old workaround quietly gets retired
- They come back asking for the next one
Shipped is not the same as used
What you get
Partners who can ship
02
Software
The same team writes it. Custom tools, data, and AI in the workflow — designed and shipped by the people who took the brief.
03
Implementation
We put the system into daily work and stay until it’s the default path — adoption is part of the engagement.
Companies that trust us
88 Arches, RECET, VA & Inc, Lamplighter Energy, Vitaro, BuildFlow Document Solutions, Langham Logistics, Morgner
Ready for counsel that ends in software?
Tell us what the team is trying to get done. We'll help decide what's worth building — then we'll build it.