Systems we've built, running every day.
Client names stay private unless they say otherwise. Here is what a full build looks like, from the pipeline that produces each issue to the desk that runs the business around it.
One operator. Three issues a week. A complete newsletter operating system.
An independent B2B trade newsletter was running on manual research, spreadsheets and a crowded inbox. We built a pipeline that researches, drafts, checks and schedules every issue, and a desk that handles sponsors, outreach, analytics and growth around it. The editor still reads every issue and presses send.
The production pipeline
- SourcesTrade feeds and public data APIs
- ResearchStories ranked by source quality
- DraftAI writing in house style
- ChecksCitations, grounding, tone
- RenderTemplate and sponsor slot
- Editor reviewHuman approves every send
- SendScheduled in the ESP
The desk around it
- Sponsor CRMPipeline, booking calendar
- Contracts & billingE-signed IOs, Stripe invoices
- OutreachProspecting and sequences
- AnalyticsIssues, subscribers, revenue
- GrowthPaid social, enrichment, ad studio
From a crowded inbox to a system that runs itself.
-
Where it started
One operator, three issues a week. Research meant working through around ten trade sources by hand. Sponsors lived in a spreadsheet. Everything else lived in the inbox.
-
What we built first
A production pipeline: story discovery, source-ranked research, AI drafting in the house style, citation and grounding checks, template rendering and a scheduled send. The editor kept final say on every issue.
-
What came next
A desk around the pipeline: sponsor CRM and booking, e-signed insertion orders with Stripe invoicing, automated outreach, an analytics view, and paid social and enrichment tooling for growth.
-
How it runs today
The pipeline has produced every issue since May 2026. The operator reads, approves and presses send, then spends the rest of the day on the work only a person can do.
Everything the business needs, on one screen.
| Date | Sponsor | Status |
|---|---|---|
| Today | Northwind Freight | In issue #212 |
| Thu | Lumen Analytics | Creative in |
| Fri | Harbor Payroll | Needs copy |
| Mon | Fieldnote CRM | Paid |
| Tue | Atlas Insure | Invoiced |
- MonetizationFieldnote CRM replied to outreach. Deal created.
- MonetizationIO-0193 signed. Slot booked, invoice sent.
- OperationsNorthwind ad placed in issue #212.
- Growth84 Meta signups synced and enriched.
- OperationsDraft for issue #213 ready to edit.
| Signed up | Subscribers | Still reading |
|---|---|---|
| Sep, week 1 | 812 | 84% |
| Sep, week 2 | 774 | 88% |
| Sep, week 3 | 905 | 79% |
| Sep, week 4 | 921 | 83% |
Illustrative example of an Inkwell-built operator desk. Names and figures are fictional.
One build, most of what we do.
This project touched nearly every part of our work. Yours might need one piece or all of it.
See all services- AI research and drafting
- Citation and grounding checks
- ESP integration
- Template rendering
- Sponsor CRM
- Booking calendar
- E-signed insertion orders
- Stripe invoicing
- Automated outreach
- Analytics desk
- Paid social tracking
- Subscriber enrichment
Let's build yours.
Tell us how your newsletter runs today. We'll show you what a system like this could look like for your team.