Open standard · Definition v1.0
Software that works for you. Not software you work.
Software as a Partner (SaaP, pronounced “sap”) is software that works on a person’s behalf instead of waiting to be operated. A SaaP product remembers the context of your work, acts between your visits, and is accountable for outcomes, while you stay in charge by approving, delegating and directing.
The definition
Software as a Partner (SaaP) is software that takes ownership of work on a person’s behalf, carries the context of that work forward over time, and answers for the outcome, while the person keeps authority through approval, delegation and direction.
Three properties
What makes software a partner, not a tool
Context
ToolStarts fresh every session.
PartnerRemembers your work, your decisions and why you made them.
Initiative
ToolWaits until you open it.
PartnerWorks between your visits and brings you progress.
Accountability
ToolAnswers for a feature working.
PartnerAnswers for an outcome landing.
Augment, not replace
One person, the reach of a team
SaaP doesn’t remove the human. It moves them up a level, from operator to principal. The partner takes the follow-ups, the formatting and the hundred small tasks; the person keeps the judgment, the taste and the final say.
SaaP bills like software but adds capacity like a teammate, without the cost of one.
| SaaS | SaaP | |
|---|---|---|
| Who does the work | You, inside the product | The partner, on your behalf |
| What you see | Dashboards, settings, forms | Proposals, progress, decisions |
| Your verb | Do | Approve, Delegate, Direct |
| Success looks like | More time in the app | Less time in the app, more done |
| Value over time | Cost grows with seats | Value grows as context compounds |
The SaaP Test
Five questions. All five must be yes.
- 01
Does it remember?
Context carries from one session, and one channel, to the next.
- 02
Does it act without being opened?
Work happens between your visits, and it brings proposals, not a blank prompt.
- 03
Does it own an outcome?
It is judged on whether the job got done, not whether a feature ran.
- 04
Are you still in charge?
You can approve, redirect or stop it, and see what it did and why.
- 05
Does it add capacity, not work?
You spend less time operating software because of it.
The SaaP levels
From tool to trusted partner
The levels describe the relationship, not the technology. Level 3 is where software becomes SaaP.
- L0ToolYou do the work.
- L1Assisted toolAI helps you do it faster.
- L2Task agentDoes a task, then forgets.
- L3PartnerRemembers, proposes, executes, reports.
- L4Trusted partnerRuns on standing approvals.
From the blog