Skip to main content
A Kennett Revenue Architecture practiceStart a conversation
Menu
Live WireIndustry signals for local media, updated through the business day →

The tools I use. The work they make possible.

A personal follow-up. A better-prepared meeting. An offer with the economics inside it. These are systems I use in my own practice. Explore my day, then imagine what the same approach could mean for your team.

— My working day. Your team’s possibilities.

Here’s how I use it.
Imagine your seller.

A client meeting to prepare for. An offer to work through. A follow-up I promised to send. These tools have a job in my day, and something useful to show for it.

Walk through the work with me. Then imagine the same approach helping a media seller, an account team or the people running your business.

In my day

I start with the conversation already in view.

Before a client meeting, I bring back the history, the open questions and the work we have already done. My assistant helps prepare a brief so I can concentrate on the decision ahead.

Client context · meeting briefs · saved documents

What I carry forward
What changed? What did I promise? What do we need to decide?
See how I prepare →

Now imagine your media seller

Imagine a seller walking into the advertiser meeting with the owner’s last concern, the previous recommendation and the unresolved question already in view.

In the advertiser’s world
Northstar wants booked inspections. Confirm the service area and how appointments are counted.

Illustrative application · Northstar Roofing is fictional. We adapt the workflow around your people and tools.

The seller is the beginning. The whole team benefits from a clearer handoff.

For sellers & account teams

Selling to local businesses

“What would make this a better customer conversation?”

Turn the business owner’s goal into a useful brief, compare planning choices and carry the reasoning into the proposal and next account review.

Local Media Desk · Meeting → Revenue Actions · Renewal Radar

Follow a seller’s day →

For publishers, general managers & operations

Running the media company

“What does this offer take to deliver—and what do we keep?”

Put price, scope and delivery effort in the same conversation. Explore the assumptions behind margin, staffing and the next investment.

Offer & Margin Modeler · Media Economics Desk · Model Desk

Work through an offer’s economics →

For audience & product teams

Growing the audience relationship

“What would give people a reason to come back?”

Use audience and subscription data to examine engagement, choose a conversion or retention experiment, and give the team a rhythm for learning.

Engagement Score · Habit Floor Audit · Reader Revenue Sprint

Explore audience & reader revenue →

We choose and adapt the tools around your operation. Start with one account, one offer or one handoff that deserves to work better.

— Inside my working day

The meeting is where
the work begins.

I capture in-person and online conversations, along with selected screen views and supporting documents. Then I use that material to work through what we decided, what is still open and what each person owes next.

The meeting record brings together decisions, objections, opportunities, tracked commitments and a reasoned view of the deal. It gives me a starting point for the proposal, follow-up and next conversation.

Illustrative meeting record · fictional publisher

Harbor County Media: an advertiser-package pilot.

One conversation. Follow the material into the decisions and work it creates.

In the conversation

“Let’s start with three advertisers. One revision round. We need to check delivery time before we expand.”

The transcript keeps the reasoning available: the publisher wants a repeatable offer, while operations is concerned about work growing beyond the price.

Shared on screen · illustrated materials

Delivery estimate
Hours per advertiser
6 hours
Loaded hourly cost
$75

12:40 into the meeting

Pilot outline

3 advertisers

1 revision round

Review hours before adding accounts.

18:15 into the meeting

Selected stills keep what was shown alongside what was said. I can return to the material when I check the assumptions.

— Now imagine your media seller

Keep the business need alive after the call.

Northstar’s owner wants qualified inspections in three towns. Imagine the seller returning with that constraint, the measurement question and the promised next step still in view—then using Local Media Desk to develop the recommendation.

The account manager can see what was promised. Operations can see why the scope took that shape. The next meeting begins with the work still to do.

Follow the seller from conversation to recommendation →
Read how the meeting carries into my work →

Make the next conversation easier to start.

The encounter is only the beginning. These are two ways I turn what we discussed into something useful you can come back to.

Built Revenue’s numbered card and its promise of a personal follow-up

One handoff. One link worth keeping.

I capture who I met and what mattered. Your card then opens a page written around our conversation: what we discussed, what I said I would send and where we could go next.

Follow a card from handshake to page →

Illustrative roundtable · fictional participants

One discussion about growing revenue.

The publisher asks about margin. The sales leader wants better follow-through. The operations lead is losing time to handoffs.

For the publisher
An operating-model example to explore.
For the sales leader
A call-to-follow-up workflow to try.
For the operations lead
A buildout example that connects the handoffs.

Each page carries the context and next step relevant to that person.

One table. Individual relevance.

Photographed business cards become contacts. The shared recording, table notes and individual interests shape a personal page for each person, with resources drawn from the work I have already published.

See how table follow-up works →
A fictional recipient’s follow-up page showing what was discussed, promised resources and a next step

A page with a reason to open it.

The result gives someone a useful place to return: the details of the conversation, a few relevant resources and a next step they can respond to.

Screenshot from the working software. The person, event and publication shown are fictional.

— The tools can join the conversation

An assistant with something useful to work with.

Through MCP, a connection between an AI assistant and business software, selected records and tools can become part of the conversation. In Built Revenue, that can mean retrieving a saved draft, bringing back client context or running a commercial calculation.

Local Media Desk has its own connection for account research, planning choices and proposal drafts. Your team brings the question and decides what to take forward.

Your people

Set the direction.
Shape the recommendation.

Connected assistant

“Continue this proposal.
Show me the choices.”

The working tools

Context & saved work.
Calculations & planning.

Illustrative request. Each connection works with the tools and records available to it.

— The Wider Build

Products I run.

Local Media Desk

Revenue operating system for local media

One campaign record from pitch to results: AI Visibility reports, market research, planning and proposals, search campaigns, orders, creative review and client reporting, with a white-label option for client pages. Political advertising operations and events run as distinct lines of business.

Model Desk

Live operating models from the workbook you already run

Turns the operating workbook a finance team already keeps into live, interactive software, checked cell by cell against the spreadsheet's own math.

AI Readiness

Choose the AI investment worth funding

A paid assessment that brings leadership and operating perspectives together to identify the AI investment worth funding, with a business case and a 90-day plan.

Seiche

Civic intelligence for local news

Helps local publishers turn fragmented public information and reporting into a persistent, source-linked civic record, so communities can see what is changing and what happens next.

Visit Seiche ↗

Seiche name pending trademark clearance.

Discoverability OS

Search and answer-engine fixes, shipped as code

Audits a site for how search and answer engines read it, keeps the evidence behind every finding, fixes the root cause on an isolated branch and opens a reviewed pull request.

In the shop

— Built for clients

Platforms clients run as their own.

Some of the work belongs to the client from the first commit. These are described by what they do; the names and links stay with the clients who run them.

Agency operating platform

The operating system for a revenue agency: account structure and health, project hubs that hold decisions, promises, meetings and documents, document search with citations, an outcome engine that estimates effort from the agency's own history, approval-gated client deliverables and a client portal that shows only released work. Agents propose the next step; a person approves it before anything is sent.

Event platforms

A conference hub for a revenue event, with attendee and sponsor portals, self-serve sponsor profiles and materials, and public sponsor pages the organizer controls. Sourced networking guides and session recaps for an industry conference. And inside Local Media Desk, events run as their own line of business, with sponsorship packages and event P&L.

— Run here first

This practice runs on what I build.

The same approach carries through the rest of the practice: the day begins with context, proposals keep the scope together, and clients have a place to find the work. Each system removes a handoff that used to depend on someone remembering.

Built Revenue Agent

The assistant this practice runs on

Built Revenue Agent is the connected working environment behind Pepper, my day-to-day assistant. It carries the briefings, meeting records, mail drafts, follow-ups and coding handoffs below, and I decide what goes out.

See Built Revenue Agent →
  1. Meet someone

    A photo of a business card, or a whole table's stack of them, is read into contacts. A follow-up page for each person is drafted from my notes and our recorded conversation, drawing only on material that already exists.

    How card follow-up works →
  2. Hold the meeting

    Meeting notes and recordings become briefs, decisions, commitments and follow-up drafts. The relationship history is there when the next meeting comes around.

  3. Start the day

    A morning brief brings together today’s meetings, open commitments and work that needs attention. Less time reconstructing the day; more time choosing the useful move.

  4. Answer the mail

    The assistant can prepare replies in Gmail drafts with the relevant context close at hand, so the work starts with a useful first pass.

  5. Propose and sign

    Private proposal pages keep the scope and next step in one place. Opening signals help with follow-through, and contracts can move into e-signature through the same system.

  6. Run the engagement

    Each client has a hub for the current work, decisions and deliverables. Weekly updates start from the work record, making it easier to see what moved and what needs attention.

  7. Account for time

    My attention and agent execution are recorded separately. That gives scope and capacity conversations a clearer picture of the work behind delivery.

  8. Publish

    Field Notes turn an operating point of view into something useful to share. Connected tools prepare LinkedIn adaptations and publish selected posts; site activity shows where readers go next.

    Read the Live Wire →
  9. Ship the code

    The implementation continues through testing, review and release. The person who understands the business stays involved as the software becomes part of the operation.

    The engineering standard →

Bring the operation you run today. We will work out whether the answer is one of these systems, something built on what you already have, or a tool I don’t make.

Start the conversation

Built Revenue