Product stories
Decisions from the inside, told whole: the data model, the price, what we will not build.
Stories
Publishing is the easy part: what we learned scheduling at scale
What we measure to know whether the product works
Signing up is not a signal. What we watch is the second week: what got connected, what got scheduled and who approved it.
How our Auto DM engine works on the inside
A comment arrives as a webhook, passes the keyword filter and leaves as a private message, and there is more in between than it looks.
How we decided the price
It is billed per workspace and not per seat, and what happens when someone stops paying is a product decision, not an oversight.
Why we do not charge per contact, even when it grows
A monthly limit that stops for new people instead of a surprise bill: what is already in conversation carries on and nothing extra is charged.
One workspace, many brands: the data model decision behind everything
The brand is the unit of the product: the connected accounts, the link page and the report mode all hang off it.
Why we built GoFeed: four invoices and a calendar
It did not start as a product idea. It started with a month-end close, four pending invoices and six open tabs.
The decisions, with their cost
Why a client and a brand are two different tables. Why there is no free plan. Why we do not publish to every network that exists. These are the decisions that explain how the product behaves, and they are usually only told inside the company.
They are written with both halves: what we gained by deciding it that way and what we gave up. A decision told only from its good side is an advertisement under another name.
Fourteen days to decide
Connect one account and schedule a week. If it does not fit, cancel before day 15 and pay nothing.