postoracle.com is our own venture, a LinkedIn growth platform where outreach, marketing content and most product work run on software. The founder writes tasks to a board and reviews what ships. Roles a team would normally be hired for are a software bill instead. The site is live and taking sign-ups, so you can check it yourself.
- Problem
- postoracle.com is our own venture, not a client engagement. A LinkedIn growth platform normally needs a small team before it earns anything: someone writing outreach, someone producing and posting marketing content, and engineers shipping product changes. Each is a salary that starts before the first paying customer arrives.
- Solution
- Outreach, marketing content and most product work run on software. The founder adds tasks to a board, the software builds against them, and the founder reviews what ships before it goes live. The roles a team would normally be hired for are a software bill instead.
- Outcomes
- Outreach runs without a person sending it. The follow-up a sales hire would send is drafted and sent on software. The founder's time went to reviewing what ships rather than writing messages.
- Marketing content is produced and posted on software. Social posts and marketing copy that would fill a marketer's week are drafted and published on software, with the founder reviewing before anything goes live.
- The founder's job is a task board and a review queue. Product changes that would need an engineering team are built on software from tasks the founder writes. The hired roles are a software bill instead.
What a person still does
The founder decides what goes on the task board, reads every piece of work before it ships, and rejects what is not good enough.
Programmes this maps toCustom AI AgentsWorkflow AutomationCheck it yourself at postoracle.com
The situation before
postoracle.com is our own venture, not a client engagement. It is a LinkedIn growth platform: people sign up, connect their LinkedIn account, and the platform grows their presence for them. A product like this normally needs a small team before it earns anything. Someone writes the outreach. Someone produces marketing content and posts it. Engineers ship product changes in a steady stream. Each of those is a salary that starts before the first paying customer arrives, and each is recurring work with a clear shape: the same sequence, repeated, with different names and dates each time.
We set out to run the company without hiring for those roles, and to find out how much of the week could be written down precisely enough for software to do it.
What now runs on software, and what a person still does
Outreach runs on software. Marketing content is drafted and posted on software, including the social posts that bring people to the site. Most product work runs on software too: the founder adds tasks to a board, the software builds against them, and the founder reviews what ships.
That review is the part a person still does. The founder decides what goes on the board and in what order, reads the work before it goes live, and rejects what is not right. The judgement about what the product should be, and whether a piece of work is good enough, has not moved. What has moved is everything between the decision and the finished piece.
The roles a team would normally be hired for are a software bill instead. That is the honest shape of the saving: not a figure we can quote, but a set of salaries that were never paid.
What you can verify
The site is live at postoracle.com and taking sign-ups. You can create an account, connect a LinkedIn profile and see the product as a customer sees it. The marketing that brought you there was produced and posted the way described above. We do not publish metered figures for this venture, because we do not have figures we would be prepared to source, so we ask you to check the product rather than take a number on trust.
What this proves about our practice
Two things. First, that recurring work can be specified precisely enough for software to do it. Outreach, content and product changes are each written down as a sequence with a clear stopping point and a person at the end. Second, that we run that software ourselves every day. Every method we sell to a business has been used on a company we own, where the cost of getting it wrong lands on us. When we tell you a process can run itself with a person reviewing the output, this is where we learned what that sentence means, and what it does not.
The one ask on this page
Ninety seconds now. Thirty minutes if it is worth it.
Take the check, see your score with no email asked for, and decide whether the thirty-minute review is worth your time. If you already know the process, skip the check and tell us.