Next Project Book a discovery call

Insights: how we publish what we learn

What we write about, who writes it, and why we publish only work we have run ourselves. The full article index lives on the Next Project blog.

Path
/insights/
Updated

Insights is where our team writes down what a project taught us. The rule is simple. If we have not run it, we do not publish it.

The article index lives on the blog. This page explains what you will find there.

What we write about

  • Scoping and discovery: how to cut an idea to a first build
  • Engineering calls that still hold at scale
  • Tracking, attribution and clean funnel data
  • Technical search for apps and headless sites
  • Launch mechanics for web and mobile
  • Tying sprint priorities to cost per customer

Who writes it

The people doing the work. Engineers write the engineering pieces. Media buyers write the channel pieces. An editor tightens the words. Nobody ghostwrites a topic they have not touched.

Our standard

Short sentences. Named tools. Real trade-offs, including the ones that went badly. Every claim either sourced or removed.

We do not publish on a quota. A month with nothing worth saying is a quiet month.

Why we bother

Two reasons, and we will state both. It helps founders make better calls, even the ones who never hire us. And it brings us the kind of client who reads before they buy. That is a good filter.

Suggest a topic

Stuck on something we have written about, or should have? Write to [email protected]. We answer questions from readers, and good questions often become the next piece.

Read the index on the blog.

Ready to scope the next step?

Tell us what you want to build or fix. We reply with a plan, a rough budget and a start date. No slide deck first.