For practitioners
For the one-person solution provider: the person who uses the AaSS (Agent as Software Solution) method to solve other businesses’ problems.
The category spreads through people who practice it.
SaaS spread because thousands of companies became SaaS vendors. AaSS spreads when many people practice it.
The one-person solution provider is that someone, multiplied. The community doesn’t just teach owners; it trains the people who will do this for the owners who never will.
This is also where the snake oil is thickest (“start an AI agency this weekend”). So the method comes with a code of practice. It doubles as the quality standard for the term itself.
The code of practice
The client owns everything from day one
Repository, database, server account and the agent’s notes, all in the client’s name.
Scoped access, in writing
A one-page access sheet saying what the agent can touch, and who approves what.
Tests before trust
Nothing changes the client’s numbers without tests and a person’s sign-off.
Say what you can’t do
No certifications you don’t have, no hours you can’t promise.
Teach as you go
Hand the client their own rod, too.
Pass both tests
If your client can’t leave you, you’re not doing AaSS. You’re doing SaaS with extra steps.
No income claims, ever.
Businesses pay for solved problems, and people do this work today. But nobody can promise you an income, and we won’t. Know the problem, not just the tool. Start with a business you understand, and follow the practitioner code.
The community is where this gets taught: how to scope a client’s problem, write the access sheet, put together the handover pack, and follow the code of practice.
Businesses are glad to pay someone who solves their problem: a solution, not just more software.
Start where the teaching is.
AaSS.communityOr take the free kit first, by email.
Not wired yet. The kit goes live with the form, and nothing is collected until then.
The community lives at AaSS.community