Product decisions and progress
What IPI has shipped—and why it matters.
This page records the public product and editorial decisions that made IPI easier to understand: what changed, why it changed, what it still does not prove, and what the next release must earn.
July 8, 2026 — Explain IPI before asking for an account
The problem was not a missing list of features. A serious buyer needed to understand the argument first: why task status cannot settle whether work counted, why proof needs context, and why completed decisions should become company memory. IPI opened a public English and Japanese reading surface so that reasoning exists before the product asks for trust.
July 10, 2026 — Compare tools by the job they actually do
The comparison guide was built around a fair premise: Asana, ClickUp, Lattice, Time Doctor, Guru, Trainual, Confluence, Scribe, Notion, and Process Street can all be good at their primary jobs. The useful distinction is where each job ends—and whether the team still lacks a line from objective and proof to human judgment, outcome, and memory.
July 12, 2026 — Make operational memory commercially explicit
Inherited Will became a plan-relative IPI add-on with a visible schedule: Starter $1,800, Growth $5,040, Scale $9,257.14. The decision matters because “company memory” should not be a poetic promise whose cost and position appear only after interest. Buyers should be able to inspect what the product is and how it fits.
July 16, 2026 — Replace search scaffolding with editorial work
Early Google results exposed two quality failures: the domain appeared where the company name should be, and an internal label appeared in a title. The response was not a one-line rename. Every English and Japanese title was audited, broken descriptions were rewritten, the company name signal was tightened to IPI, and the shared article system was rebuilt around narrative, visual hierarchy, and human authority.
What this progress does not prove
Publishing a page does not prove that Google will index it, rank it, or immediately display the preferred site name. A comparison does not prove that IPI is better at a competitor’s primary job. A polished story does not replace product evidence. These pages state the product’s reasoning clearly; search systems and buyers still have to evaluate it.
What the next release should earn
The next public improvement should come from stronger evidence: real work-cycle examples that can be shared responsibly, clearer product demonstrations, and buyer questions the current explanation fails to answer. Building in public should make the argument easier to inspect, not simply create more announcements.
FAQ
Why publish the decision behind a product change?
A feature list shows what exists. The decision explains which operating problem the change addresses, which trade-off was accepted, and what evidence should determine whether it was worthwhile.
Does publishing progress prove the product works?
No. Public progress makes the argument inspectable. Product evidence, responsible examples, and buyer outcomes still have to earn the stronger claim.