Tertium · Work with me

Work out what you’re building. Then build what makes it run.

Most projects that reach me are half-formed. The idea is real and the people are good, but nobody has yet said plainly what the thing is, who it serves and what has to be true for it to work. I start there. Then I design and build the system underneath it, and hand it over.

Two engagements

Two ways the work is done.

Launch & Build

For founders and mission-led organisations: a school, a publisher, a clinic network, a firm that has outgrown its first description.

We define the thing (positioning, offer, audience, the decision about what it’s for), then build what runs it: go-to-market, roadmap and OKRs, brand and content operations, CRM and automation, measurement you can read without calling the person who built it.

Recent work

A mental-health network launched across two funnels, with three ad accounts recovered and blended cost per lead cut by two-thirds; a philosophy imprint’s US operation built from the ground up, eight monthly editions without a missed launch; brand and operations for a UAE Arabic-teaching institution. (Full entries on LinkedIn.)

Joshua Beneventi in conversation with Rehan Khan, 2026 — In conversation with Rehan Khan, 2026.

Development

For scholars, authors and teachers with a body of work.

Shaping a book or a programme of work (the argument, the structure, the research behind it, the path to a finished manuscript), and building the engine that carries it to readers: a searchable archive of your sources, a publishing pipeline with human approval at every public step, and an analytics loop that shows what landed. Current work: research and editorial support on two books at the Kroc School, University of San Diego.

Proof: my own engine

A research archive of more than 3,000 transcribed talks, a source-led cascade from essay to carousel to Substack, and an analytics loop, behind an audience of 63,000.

In conversation

How it runs

Map, design, build, hand over.

MapRead into your materials, your tools and the way work actually moves, and write down what exists and what depends on one person.
DesignA few possible shapes with what each costs to build and keep alive, a recommendation, and the human gates named.
BuildWeekly steps you can see and use: something real to review each week, not a status report.
Hand overDocumentation for the next person, a working session with each user, and a runbook for what breaks.

Each phase has an end. The scope and the closing date are written in the first week. Nothing renews by itself. Everything lives in your accounts. A machine can sort, draft and check; a person decides and signs.

Ways to begin

Strategy sprint: 2 to 3 weeks; The map and the design, with a recommendation you can act on alone.
Full engagement: 6 to 12 weeks; Sprint plus build and handover.
Stewardship: Monthly, after a build; Care for the system once it is yours.
Book development: Scoped per project; The Development engagement, shaped around the book.

Coaching

For one person at a threshold

A role, a vocation, a chapter without language yet: a 90-day arc on the same Socratic method. See coaching →

Start with a conversation →