What this is

ActionAmp maintains a public roadmap at actionamp.com/roadmap. The page works as both product documentation and a public record: its shipped log gives every entry a date, its phases state where the product stands rather than when it will arrive, and it counts its own activity for anyone to check.

This note covers the decision behind that page — why it records instead of promising.

The friction

A studio product that develops quietly looks, from the outside, like a product that stopped. The usual fix is roadmap material, but conventional roadmaps trade in promises: quarters, feature dates, countdowns to launch.

Each of those promises creates its own pressure. Announce a quarter and the calendar starts making product decisions. Run a countdown and the launch date arrives whether the funnel is ready or not. A traditional backlog adds a slower decay — items pile up, rejected ideas stay listed as if they were still candidates, and the page begins to describe a product that does not exist.

For a self-funded studio, none of that pressure buys anything. The work was happening. The problem was that nobody outside the studio could see it.

The senior decision

We made the shipped step the public unit.

The roadmap’s log records what became real, each entry with a date, back to the first one on June 16. Now, Next, and Later carry the direction, and each item states where it stands in verification rather than when it is due. Ideas that are off the path — note-taking, in-app storage, calendar sync — sit in an explicit won’t-do state instead of lingering as quiet candidates.

Open launch follows the same rule. No countdowns, no launch dates until the numbers say go. Priority access goes to founders and first-time builders while the product is soft-launched.

The trade-off is real: competitors can read the plan, there is no countdown to market around, and the page must be maintained or it starts to lie. What it buys is a page that proves the work instead of promising it.

What became real

The roadmap is live with a shipped log that runs from the marketing site’s first step through capture image intake and beyond. The page reports 37 shipped features and 804 commits since June 16.

The phases match the product’s actual state: Foundation is shipped. Now marks the MVP as live, with items in verification. Next prepares for first users — the newsletter, the retention critical path, Google sign-in. Later names what comes beyond the first users.

Evidence

The roadmap is live. A visitor can count the dated shipped entries, read the won’t-do list, and check each phase’s state.

The counters are the page’s own report; the shipped log they summarize is inspectable entry by entry. The claim this page makes is the one a visitor can verify by counting.

What we learned

A record of shipped work does the studio’s marketing without a pitch. Dates, commit counts, and phase states persuade quietly, and the log grows more convincing with every entry.

Announcing a date borrows attention now and repays it in pressure. Direction without deadlines kept the launch timing in the hands of evidence.

Current state

The roadmap is live and the shipped log grows with each step. The phase gate still stands: open launch waits for funnel evidence, and the founding-member offer remains the way in.