AI One-Person Company
5 articles about "AI One-Person Company".
AI Skills Are an Injection Path Too: Scanning 954 Popular Skills, and an Eighth Question Before Buying an AI System
A September 2026 paper scanned 954 popular AI agent skills. Its tool flagged 17.6%, and reviewers confirmed 84 of 100 sampled findings as latent vulnerabilities. Five skills were attacked for real and 13 of 30 attempts succeeded, even when models recognised the risk. Around the same time Microsoft disclosed two 9.9-rated Semantic Kernel vulnerabilities, and both arrive at the same line: the model is not a security boundary. This post unpacks the qualifiers on each number and adds an eighth question to our seven questions to ask before buying an AI one-person-company system.
How Much of Claude for Small Business Works in Taiwan? 37 Connectors and 43 Workflows, Checked One by One
On 15 September 2026 Anthropic expanded Claude for Small Business to 43 workflows and 37 connectors, and every workflow waits for the owner's approval by default. But most of the payments and payroll tools on the list do not serve Taiwan: Stripe, Square and Shopify Payments do not accept Taiwanese merchants, Gusto is a US payroll system, and LINE, ECPay, Shopee and Taiwan e-invoicing are absent. This post checks what connects, what does not, and why the approval mode is worth copying.
How an AI One-Person Company Actually Runs: The Split, the Lines, and the Mistakes
What it actually looks like when one person plus AI runs an AI product company. This post collects the practices we have published: strategy and veto on the upper layer, construction on the lower layer, only a human presses publish; own product and partner product split into two lines that never share a window; three things never outsourced: shipping, external promises, breaking spec; and why silent failure is the biggest enemy. Everything comes with verifiable records, including our own mistakes.
Seven Questions to Ask Before Buying an "AI One-Person Company" System
"AI employees" and "one-person company systems" are multiplying, priced anywhere from a few dollars to hundreds. Before paying, get seven answers: what exactly is delivered, what machine it runs on, whether the refund promise and the terms of service say the same thing, whether there is real operating evidence, whether the seller uses it, whether the items in the value stack can be bought separately, and what updates and community actually mean. At the end we run the same checklist against our own handbook, including the boxes we fail.
What Is an "AI Employee", and How Is It Different from an AI Tool? One Account That Actually Runs
"AI employee" is a product narrative; underneath it is still a model plus a set of rule files. The real difference is four things: shared memory, whether the rules can override the model's own templates, a review gate on output, and who is accountable when it goes wrong. This post uses one of our own Threads accounts, run by an AI agent since September 3: the first real run surfaced five defects no spec revealed, compliance went from 0/4 to 5/6, and two things are still judged by a human.