We build software the way operators actually work.

Most newsletter teams have been sold software built for someone else. We start with how you actually work, then build around it.

Start a project How we work

Illustrative example of a discovery workflow map. Names and figures are fictional.

Our philosophy

Built with you, not handed to you.

Fifteen years of running newsletters, paired with modern engineering and AI. Everything we build is yours to keep.

One tool or a full operating system, it starts the same way: a conversation about how you run today and where the hours go.

How an engagement runs

From first call to a system your team runs.

  1. Discovery callHow your newsletter runs today and where the time goes
  2. Workflow mapEvery step, tool and handoff, plus a scoped plan
  3. First releaseA working tool your team uses within weeks
  4. Build outRelease by release, shaped by real send days
  5. SupportWe monitor, maintain and extend as you grow
How we work

Six principles behind every build.

  1. Start with how you run today

    We begin by mapping your workflow end to end: who touches each issue, where the spreadsheets live, which steps are manual, and where things break.

  2. Design around your team

    Every system fits how your organization already works, from one person doing everything to separate editorial, sales and growth teams.

  3. Ship in weeks, not quarters

    We build in small, working releases, so you are using real tools early and every step is shaped by what actually happens on send day.

  4. Keep a human in the loop

    Automation and AI do the heavy lifting, but people approve what goes out. Nothing reaches your readers or sponsors without a review step.

  5. You own everything

    The code, the data and the accounts are yours. No proprietary platform, no lock-in, and clear documentation for whoever works on it next.

  6. We stay on

    Newsletters change every week. We support, monitor and extend what we build, so the system keeps pace as you grow.

Ways to work together

Start small or build the whole system.

Every engagement starts with discovery. Then pick the shape that fits.

Workflow audit

A focused review of how your newsletter is produced, sold and grown. You get a workflow map, a prioritized list of what to build and a scoped plan. It is yours whether or not we build it.

  • Workflow map
  • Opportunity list
  • Scoped plan
About the workflow audit

Custom build

We design and build a defined system, such as a production pipeline or an outreach and ad ops engine, shipped in working releases and handed over with documentation.

  • Working releases
  • Documentation
  • Full handoff

Build and run

For teams that want a long-term partner. We build it, then run it with you: monitoring, maintenance and new releases as your newsletter grows.

  • Ongoing releases
  • Monitoring
  • Priority support
What you get

Software you own, and a team that stays.

Workflow map and plan

Every step, tool, owner and handoff in your newsletter today, with a prioritized plan for what to build first.

Working software

Real tools your team uses from the first release, built inside your own accounts and connected to your ESP.

Documentation

Plain-language guides for your team and technical docs for whoever maintains the system next.

Access and ownership

All code in your repository, all data in your accounts, all credentials under your control.

Training and handoff

Walkthroughs with the people who will use each tool, so the system is adopted, not just delivered.

Monitoring and support

Alerts when something breaks and a team that fixes it, for as long as you want us around.

FAQ

Working with us.

The practical questions teams ask before an engagement starts.

Do you work with our in-house developers?

Yes. We can build alongside your engineering team, follow your code review and deployment process, or take on newsletter systems so your developers can stay focused on your core product.

How do you handle access and security?

We work inside your accounts with the minimum access each tool needs, keep credentials in your own secret stores, and follow your review and approval requirements. Larger organizations can bring their own security checklist.

What does an engagement cost?

It depends on scope. After the discovery call we send a scoped plan and estimate for the first release, so you know what you are getting before any build starts.

What if we only need one tool?

That is a great place to start. A single pipeline, outreach system or internal tool is a focused first project, and the system can grow from there.

Who owns what you build?

You do. The code, data and accounts are yours from day one, with documentation for whoever works on the system next.

Partner with Inkwell

Start with a conversation about how you run today.

No pitch deck. We'll walk through your workflow together and tell you honestly where software would help.

Start a project How we work