Practice
— version one
The thesis of the practice, the choices behind it, and how an engagement runs. A working specification — to be revised as the practice evolves.
§ 01 — The Reading
A practice that remembers.
Twoen Consulting is a fractional CTO practice for founder‑operators who'd rather steer their business through dialogue than dashboards. The bet is that work should compound — and that the system you talk to should still know what was decided last quarter.
The friction is mostly memory. The hard part of running a business isn't deciding things — it's holding onto what was decided. Files in one place, conversations in another, the reasoning behind both nowhere durable. Three months later: where did that decision live? Whose folder, whose chat thread, which session, which call? Every meeting opens with level-setting, and sometimes the whole hour is level-setting. Universal experience. Necessary work — but a tax that compounds the wrong way when nobody's paying it down.
This practice runs on a different premise. The offer is a partnership — a platform built for exactly these problems, alongside someone who's been an operator himself. Your technology choices are respected. Your priorities are respected. The advisory orients; it doesn't push or pull. The platform doesn't relitigate what you've already weighed and chosen.
The platform sits between you and what you already run, carried through conversation. It remembers what crosses your desk — level-setting still happens, but the system pays it down instead of the meeting. That memory is your leverage. The mission is growth; modernization is what growth requires, when growth requires it.
That premise is also why this document looks the way it does. The page-and-card brief that introduced the brand argued for editorial restraint, numbered sections, and one accent used surgically. The same hand wrote the engineering. So this introduction is structured the same way — because, on this practice, that is the introduction.
§ 02 — Five Concrete Choices
The choices that shape the practice.
Each followed from the same thesis: that operators don't lack tools, they lack continuity. Listed in roughly the order they got locked in.
-
01
Memory, not dashboards.
Most operational tools optimize for visualization. Twoen optimizes for recall. The premise: numbers will look at themselves, but reasoning needs a place to live. The platform is built around that single asymmetry.
-
02
Up to twelve, deliberately.
Most consulting practices scale by adding bodies; the founder's voice gets diluted by the third hire. Twoen scales by adding context — and the roster is capped at what one principal can hold with platform support. Saying "no" is part of how the practice maintains its register.
-
03
Wrap the stack, don't replace it.
Your existing tools stay your existing tools. Your scripts, your workflows, your chat surfaces — the platform sits above what you already run, holding what crosses your desk so it can be picked up later. Integration over migration; adapters over forklifts.
-
04
Stand on your work.
The platform sets you up to pick up where you left off — what was done, what's next, what's left. Every session stands on the prior one instead of starting from "where were we." The work you've already done becomes leverage; the platform is the surface that puts it back in reach.
-
05
For founder-operators, not committees.
The model assumes one decision-maker on the other end. Founders, principals, owner-operators running their own thing. The practice is calibrated to that velocity — fast turnarounds, direct talk, decisions in the room, execution that follows.
§ 03 — How An Engagement Runs
Three modes, one posture.
Three modes, scoped distinctly. The platform runs continuously. Integration is bounded — we wrap the processes that matter, not every one. CTO time is scheduled. Day-to-day support sits outside the plan; the practice is available, but not on call.
2n runs whether you're on a call or not.
- What it is
- A continuity layer on a per-tenant VPS. Listening, recording, compiling state from every signal. Holds the institutional memory of the business, addressably.
- What's included
- Monitoring and maintenance of the platform itself, ongoing. That's part of the plan.
What matters, not everything.
- What it is
- Adapters from your existing tools into the continuity layer. Front-loaded — about a week of integration work for a chosen set of business processes.
- What it isn't
- Replacing your stack. Forklifting anything. Wrapping every process you run. The wrap is invisible at runtime, and the goal is leverage, not coverage.
The decisions that need a CTO in the room.
- What it is
- Scheduled CTO reviews on a bi-weekly or monthly cadence. The platform surfaces what's pending; the review works the calls that need working.
- What it isn't
- Day-to-day operations or break-fix. Available — not on call. The platform handles the lifting; the practice handles the calls that actually need a CTO in the room.
§ 04 — The Platform, In Modules
A short list, used together.
The 2n platform is built from a small number of pieces, each doing one job. The same restraint applied to color — every accent has to earn it — applies here. No module without a reason.
Continuity
Event Ledger
Append-only record of every signal — voice, text, file, system event.
Distill
State Compiler
Compiles continuity into maintained operational posture.
Cognition
Control Plane
Routing, normalization, governance. The traffic director.
Insight
Reporting Layer
Daily synthesis from canonical state. What changed, what matters.
Conversation
Talk to it
Send messages, talk in the car, type at your desk. The surface that fits the moment.
Instrumentation
Execution Envelope
Structured run records. Observability without conflation.
2nbox
Artifact Registry
Files, addressable. First-class objects across surfaces.
The Operator
You
The judgment in the loop. The platform reduces load — never replaces.
§ 05 — Two Ways In
Two tiers, no middle.
Either you bring your own stack and want the engine, or you want the practice on top. The middle ground — half-integrated, half-advised — was deliberately excluded. That's the configuration where continuity erodes, and the whole reason for the platform is to keep continuity from eroding.
Personal — Tier I
For your own threads.
An author keeping a book organized. A side-of-the-desk venture trying to start. A parent running family logistics like a small operation. A high-agency person tracking too many threads at once. The shapes vary; the friction is the same one — too much context, scattered everywhere, no durable place for any of it to live.
You get the platform on a hosted and managed per-tenant VPS. Full control of your instance, but without the business-process integration. Just the engine and the continuity layer underneath it. A funnel into the practice for those who outgrow it.
- Dedicated VPS
- 2n continuity engine
- Bring-your-own toolchain
- Hosted and managed · your instance
Business — Tier II
The full practice.
For owner-operators and founders running a business — with "systems," whether they call them that or not. The practice wraps those systems so the business runs conversationally. Things that cross your desk get remembered. You pick up where you left off.
And you have someone alongside the platform — built and run his own — guiding the systems' evolution as the business scales. The mission isn't modernization. It's growth. Modernization is what growth requires, when it requires it.
- Everything in Tier I
- Wrapped business systems
- Scheduled bi-weekly or monthly reviews
- Platform monitoring & maintenance
- Long-term partnership · capped roster
§ 06 — The Calling Card
The card pointed here.
The page-and-card brief introduced the practice as a printed object. This document is what the card pointed to. Same hand, same restraint. If you got here from someone's pocket, that's the workflow operating as designed.
2n
TWOEN
twoen.ca/talk
Front · Recto
Jim Adcock
Founder·Fractional CTO
Signal+1 604 376 2468
BasedVancouver, BC
Back · Verso
Reach
Roster
A few openings.
Up to twelve, total.
Up to twelve, total.
Fit
Founder-operators
running their own thing
running their own thing