A digital-health CEO reports his businesses have no full-time developers, DevOps, designers, analysts or product manager: scheduled AI agent shifts handle deploys, an agent-built CRM, per-business-line email sorting, meeting scheduling, technical support and publishing news four times a day. The work runs on three $200 AI subscriptions — $600 a month against roughly $38,500 a month at US median pay for the replaced roles.
Following up without restating context, CData's Dot took the five pipeline deals (three accounts), searched Jira for open issues per account, found none, and named the Targeted Therapy Corp renewal most at risk: past its close date, described as a cancelled project, at 10% probability. The post says the same answer by hand can take days of asking engineering and searching two systems.
His AI rechecks all 31 providers and 89 plans on TokenPlans.dev on a schedule. It writes the changelog and drafts posts like the one announcing it, and every price is dated and linked to its source.
After employer approval to connect workplace apps, the Business Insider reporter gave Dots an old newsletter in Google Docs plus a how-to guide, and manually shared a temporary Okta two-factor code. The Dot produced a test newsletter draft in about five minutes that an editor called 95% good, with photos, a chart and links in the right places.
Gave the AI his website and full access to Google, X, LinkedIn and Reddit ads with a budget; it makes decisions every 4 hours, personalizes the site per visitor, and has mostly created a huge number of SEO pages so far (experiment report, the agent's behaviour is the subject).
This only partly worked. Worth knowing before you try it.
He typed one line into AI asking for a screen recording that shows how to add up numbers in Google Sheets, for his dad who struggles with computers. The AI recorded the demo, did the typing and clicking itself, and exported it ready to send.
Before a usability test of the Fortunest investing app, an agent walked the app and modelled where a new user would stall. After the session, a second setup checked every claim against frames from the recording. Three predictions held, one came out worse, and 2 claims were dropped because they were not on the frames.
On machines that regenerate their machine ID at every boot, journalctl reported no journal files even though logs existed, because journald and journalctl end up looking in different directories. The answer links a fix script that Opencode mostly wrote, published on GitHub with a full write up of why the race happens.
Used the AI on the 20 dollar tier in a weekend to build good enough coverage on Floci features to make it useful to him; others then continued the work.