The publishing studio
The custom CMS behind Field Notes: a markdown editor with live preview, controlled publishing, and a leads inbox. Built for the practice itself in Next.js and PostgreSQL.
The process
Vol. VI · MMXXVI
§ 00 · the method
I map how your business runs before we build anything.
Most help starts with a tool or a template. I start with how clients actually get found, sold, onboarded, delivered to, and offboarded, including the manual stitching you do without realizing it. Only then do we design and build.
§ 01 · the sequence
Four phases, in order.
Each one earns the next. Nothing gets built before it is understood.
- 01
Clarify
Start with an Operational Clarity Session: paid strategic scoping with intake, a 90-minute working session, and a written follow-up brief that names the right next step and an initial 90-day direction.
the clarity session
- 02
Onboard
Operational Onboarding is the first month of the retainer: an internal review of access, workflows, tools, risks, and context. The audit framework is used internally here to map how the business actually runs.
the retainer begins
- 03
Build and steward
The first 90-day operating cycle: one primary operational priority and one active custom development or AI automation priority at a time, with workflows refined and documented as they change.
- 04
Stabilize
Refinement, documentation, workflow stabilization, and planning the next layer. Systems drift back into workarounds when no one tends them; this keeps yours holding.
Clarify is the Operational Clarity Session; Onboard through Stabilize is the retainer. Pricing is on the Services page.
One partnership for both
Operations help usually stops where the build begins. Ours doesn’t.
The usual split
An OBM maps the problem, then hands the build to a developer who was never in the room. What comes back is technically correct and slightly wrong, or the cost of a second hire kills the idea and you settle for another workaround. Either way the thinking gets lost, and you hold both halves together.
How I work
I map the operations and design the system; my team and I build the custom tools when software won’t do the job. The diagnosis informs the design; the design informs the build. Nothing gets handed off. This is real work in Next.js, PostgreSQL, and AI-augmented development, not a theoretical capability.
Most operational partnerships top out at “you’ll need a developer for that.” We don’t have that ceiling.
§ 02 · selected work
Proof that we build, not just advise.
A few builds, shown as evidence.
The business register
A working prototype for the Bermuda Economic Development Corporation: a business register with staff review workflows, a document vault, and a work hub that routes each day’s tasks.
The full record
Bermuda Trivia · Store Tunes · Odetunde Law
The client site builds, photographed in the studio, live on the portfolio alongside these two.
§ 03 · working together
The shape of an engagement, so there are no surprises.
A partnership moves through four stages, on a predictable rhythm.
01
The Operational Clarity Session
Paid strategic scoping. I map enough to recommend the right next step and hand you a written brief.
02
The proposal
The recommended retainer or project, scoped against what the session surfaced.
03
The retainer or project
The work itself: ongoing leadership on a retainer, or a bounded custom development project.
04
Studio hours
Your standing access window during a retainer.
Cadence
Business hours, async replies inside a day or two, bounded on purpose. A partnership that burns out the people in it serves no one.
§ 04 · why I map first
Why I map first, every time.
The method comes from watching builds fail because they started in the wrong place: a portal that did sixty percent of the job, a developer solving a problem nobody had diagnosed. Good technical work, aimed slightly wrong, because the operational reality under it was never mapped. I learned both halves so the diagnosis and the build stop getting lost between two sets of hands.
The fuller story →§ 05 · begin
Start with an Operational Clarity Session.
The low-commitment way to see how I think before any larger decision. You leave with a written brief and a clear next step that are useful on their own.
Let me know your thoughts and we can go from there.