REVERSE SaaS.

We are pioneering Reverse SaaS.

Reverse SaaS is a business model. Service-as-a-Software is what the customer buys. Forward Deployed Software is how the digital worker enters the customer's business. NIKO is the first Ernesta Labs implementation.

That distinction sounds simple because it is simple. It also changes what the vendor is responsible for. The stack is our problem. The result is yours.

Ernesta Labs coined these terms independently to name this four-layer model. Reverse SaaS is the business model. Service-as-a-Software is what the customer buys. Forward Deployed Software is how the digital worker enters the customer's business. NIKO is the first implementation.

Independent coinage is not the same as claiming first public use. Our publication review found earlier public uses of some of the same words. In March 2026, Yunpeng Brian Pan used Reverse SaaS for industry operators building and spreading software. Days later, Fabio Lopes used the same title for services delivered with software-like scale. The Service-as-a-Software reversal also appeared in public investor theses from NFX and Foundation Capital in April 2024.

Those external meanings overlap and conflict. They do not contain Ernesta Labs' complete model. Our definitions and combined system are our own: Reverse SaaS as the business model, Service-as-a-Software as the purchase, Forward Deployed Software as our coined delivery model, and NIKO as the first implementation under an open falsification test.

When we say we are pioneering Reverse SaaS, we mean we independently coined, built, and are testing this specific model in public. We are not claiming that no one else ever produced the same words, that we own ordinary language, or that the model is already proven.

SaaS changed distribution. It did not remove the work.

Traditional software as a service made software easier to access, update, and distribute. Our comparison uses the default subscription model as a deliberately simple baseline: access to a tool, with the buyer normally responsible for configuration, implementation, adoption, workflow design, operation, and the gap between what the tool can do and what the business actually needs. Managed SaaS, outcome-priced software, and automation that performs real work already blur that boundary. The contrast is not a claim that every SaaS contract is identical.

A company can keep paying for software when the setup is wrong, the workflow is unused, the model produces rubbish, an LLM hallucinates, usage is consumed on work that creates no value, or the desired result never occurs. This does not make every SaaS vendor unethical. It exposes what the contract rewards.

Reverse SaaS asks a sharper question: why did a person who needed a service have to become the operator of somebody else's software?

The website analogy.

A customer asks Riccardo Jody Minniti to build a website because the customer wants the website. They do not care whether he coded every line manually, used Codex, delegated a specialist task, or orchestrated several software systems.

The service requested was: build the website. The value was: the website got built.

That is already the mental model behind Reverse SaaS. The machinery matters to the provider because the provider must make it reliable. It does not become homework for the customer.

NIKO is a much harder version of the same proposition. A website is a bounded artifact. Sales is an ongoing professional service performed under uncertainty, against real people, real objections, changing evidence, commercial constraints, and delayed outcomes.

You do not subscribe to NIKO. You hire him.

That is the intended future model if Experiment Zero succeeds. It is not a current offer.

The customer would not subscribe to an AI SDR dashboard, seats, tokens, credits, or an assistant. The customer would hire NIKO as the salesperson.

The company would tell NIKO what is being sold, its policies, its commercial constraints, the boundaries of price and negotiation, and the territory and resources he is permitted to use. Then NIKO would sell.

The customer should not need to care which model ran underneath, which database stored state, which research provider supplied evidence, which plugin was delegated, or which orchestration system recovered from failure. That machinery is Ernesta Labs' responsibility.

NIKO is B2B only in the current thesis. Ernesta Labs does not intend to deploy him to sell harmful or misleading consumer products. Client eligibility must be decided before deployment, not discovered halfway through a mission. The detailed admission policy does not yet exist and this article will not invent it.

Fair exchange, not theatrical risk transfer.

The objection is not that a provider must take every possible risk. Riccardo explicitly rejects that framing. The proposition is a commercial opportunity for both sides.

A customer has a problem. A provider believes it can solve the problem. If genuine value is delivered, both should be able to make money.

The commissioned-salesman analogy is direct. A homeowner has a house to sell. A salesperson says, "I can sell it, and I take a percentage of the sale." The relationship exists because one side needs the service and the other sees an opportunity to earn by delivering it. If the sale succeeds, both benefit.

The intended analogue for NIKO is a commission-oriented autonomous salesperson. No commission rate, base fee, monthly amount, package, tier, or final pricing formula has been decided.

Software still has operating costs.

AI compute, infrastructure, data, voice, and specialist resources cost money. A future arrangement may include a reasonable base amount that keeps the worker operating. Plugins or resources may be funded through usage, add-ons, or direct consumption costs.

Those details remain open. The principle does not:

Value first. Money follows.

We do not make money without creating value in the world.

Riccardo wants to become extremely wealthy. That is not hidden behind a performance of indifference. Money provides capability, resources, freedom to build, and scale.

But money is not the epistemic objective. It is not proof that something useful happened. A company can be celebrated through fundraising, cross-investment, valuation, and narrative without delivering equivalent value in the world.

Reverse SaaS is an attempt to tighten that gap. Ernesta Labs should earn because a service was actually delivered, not because the customer's credit card remained attached to a tool that failed to change anything.

This is not anti-capitalist rhetoric. It is a demand that exchange remain connected to something real.

The software is the employee.

Forward Deployed Software is not a new name for an agency, consultancy, BPO, or ordinary outsourcing. In those models, humans deliver the service and software may assist them.

In Reverse SaaS, the software itself is the deployed worker. It enters a company's real operating context, receives bounded authority and resources, performs the professional service, records what happened, and remains accountable to evidence.

This is deliberately different from a forward deployed software engineer. A consulting engineer is not the delivery model here. The software is.

For NIKO, the software is the salesman.

The customer experience should feel like a remote employee working continuously. You do not need to watch the worker clock in. You know the work is happening. Important events reach you. When you want detail, you inspect the record.

No dashboard theatre. No pretending that a row of activity metrics is the service.

A specialist, not a slogan about replacing everyone.

Ernesta Labs cannot promise that no human job will ever be displaced. Nobody can. The actual thesis is narrower: NIKO is a specialist for hire, closer to a commissioned salesperson, consultant, forward-deployed expert, or specialist brought in to remove a bottleneck.

Riccardo's belief is that if specialized capability creates substantial growth, that growth can increase demand for humans elsewhere in the company. That is a founder thesis, not an established economic law.

NIKO sells. His harness supplies specialists.

NIKO remains specialized in start-to-close commercial judgment. He should not become a bloated generalist merely because a commercial mission needs adjacent work.

The surrounding harness is designed to delegate to plugins that can act like employees, departments, tools, resources, or specialist capability. Examples may include lead generation, deep research, stakeholder discovery, voice, CRM operations, sales engineering, proposal production, pricing support, and industry expertise. NIKO delegates this work. He does not become it.

This is intended architecture, not proof that every plugin or delegation path works in production today. Plugin economics may differ from NIKO's outcome-oriented service economics because specialist resources carry their own usage costs.

We are not selling NIKO until Experiment Zero earns us the right.

NIKO is not currently for sale. Ernesta Labs is not asking customers to pay for an autonomous-sales claim that has not been demonstrated.

Experiment Zero comes first. Its terminal proposition is: can NIKO function as an autonomous salesperson in the real world?

Intermediate stages may calibrate identity resolution, evidence, contact readiness, transport, and bounded action. None of those stages is the final result. A signup is not a customer. A send is not a sale. Activity is not commercial proof.

The public result must be allowed to be yes or no. No predetermined victory. No hidden human closer. No second Experiment Zero under the same product claim after a fair, valid failure.

Experiment Zero does not decide whether Riccardo believes Reverse SaaS is the direction Ernesta Labs should pursue. That belief already governs how he thinks about services. The experiment decides whether this implementation earns its claim.

A close is not permission to cheat.

There are two separate questions: which clients Ernesta Labs accepts, and how NIKO sells once a client is accepted. One policy cannot substitute for the other.

Ernesta Labs is responsible for building NIKO so that his conduct does not depend on lying, sneaky manipulation, forcing somebody into something they do not want, cheating, or damaging the principal merely to maximize close rate.

Consider a negotiation band. If NIKO is allowed to negotiate between two prices, that range is discretion. It is not a loophole that means "always sell at the floor because the close is easier." A competent salesperson must balance probability of close, margin, principal interest, buyer context, and the actual authority granted.

Experiment Zero should expose the places where an autonomous salesperson exploits freedom incorrectly. Those failures should be observed, documented, corrected, and shown.

Commercial loss is not automatically wrongdoing.

A human salesperson can make a legitimate judgment inside company policy and lose the deal. The employer does not normally charge the salesperson the lost revenue. A lost deal is not automatic compensable failure.

If NIKO acts legitimately inside policy, authority, and commercial constraints and the deal still fails, that is sales. If NIKO genuinely does something wrong and the evidence establishes it, Ernesta Labs should own the error and make it right. We are not designing a giant liability regime before a public commercial test has produced its answer.

The customer should be able to reconstruct what happened.

The intended record is not a cheerful activity feed. It is observable commercial truth.

• Actions: what NIKO did and when.
• Messages: the commercial communication the customer is entitled to inspect.
• Delegations: which specialist or resource performed adjacent work.
• Sources: what evidence informed a material decision.
• State changes: how the opportunity and plan changed.
• Constraints: what authority and boundaries applied.
• Mistakes: what failed, what was corrected, and what remains unresolved.
• Outcome: how a sale happened, or why it did not.

The record should be structured enough for a customer to give it to another AI and ask, "What actually happened?" The answer should be reconstructable from evidence.

Transparency does not mean exposing another customer's confidential data, security secrets, private hidden reasoning, or chain-of-thought. It means the customer can inspect the commercial facts, decisions, authority, and outcomes that matter to the service.

No customer-service wall.

A customer who hired a service should be able to see the service, understand its state, speak to NIKO, reach a human when genuinely necessary, and cancel without dark-pattern obstruction. Refund requests should not disappear into an email maze. Support should not be deliberately hard to find.

Where possible, the software should detect and recover from its own failures. No hostage UX.

The workflow is not the moat. Experience is.

Ernesta Labs is not afraid to expose NIKO's workflow. Salespeople already publish scripts, frameworks, books, door-knocking strategies, and closing techniques. Two people can follow the same visible sequence and produce different outcomes.

The workflow changes with evidence. NIKO decides within the authority he has been given. The interesting capability lives between the obvious steps: how evidence changes judgment, when rejection formed, what caused it, what should change for this prospect, what may generalize, and what must not be generalized.

NIKO begins much like a new salesperson. He has territory. He goes out. He encounters silence, rejection, bad timing, wrong assumptions, objections, failed follow-ups, recoveries, and, if the thesis survives, eventual closes.

NIKO should not perform every post-mortem himself. The surrounding harness can analyze trajectories, locate failure, compare outcomes, test hypotheses, validate lessons, store structured experience, and feed promoted lessons back to the salesman as better commercial cognition.

Private context. Shared, validated lessons.

Customer records, private conversations, pricing, CRM history, and confidential company data must remain isolated. They cannot be mixed across customers.

Anonymized, validated, non-identifying commercial lessons may eventually improve a shared commercial model, orchestration, or NIKO capability. The claim to test is that a software worker can compound legitimate experience more aggressively than one company could generate alone.

If ten companies used NIKO, each would retain a private commercial context. Over time, all might benefit from a worker exposed to a wider range of validated commercial situations. This is a hypothesis. It is not a current result.

Speak the claim. Then have the courage to test it.

Riccardo deliberately rejected a private experiment followed by a polished success story. He does not want secret intervention, cherry-picked wins, or an ending controlled by his own interpretation.

The public should be able to watch, judge, criticize, disagree, propose alternatives, and inspect the outcome. Public exposure removes some of the founder's ability to rewrite failure after the fact.

Riccardo acknowledges that his ego can be gigantic. The acknowledgement is not a cure and it does not become evidence. Ego receives no constitutional authority over reality.

He describes himself first as a servant of Allah. His opinion can be wrong. Community opinion can be wrong. AI opinion can be wrong. Only what survives testing earns confidence.

If the experiment works publicly, the upside may be enormous. If it fails publicly, he accepts the downside. That asymmetry is part of the test, not a reason to hide it.

Community is input. Reality is the selection mechanism.

The intended community is not a founder fan club and not a noisy public chat room. The likely path is public work, then a waitlist, then a free private community for people who want closer access to research and Experiment Zero.

The expected shape is deeper research, research discussion, calls, Experiment Zero analysis, brainstorming, practical tools and artifacts, open-source discussion, and closer access to the work. The platform and exact format are undecided. No investment offer, equity promise, security, guaranteed allocation, financial reward, or guaranteed future commercial term exists.

People may join because they believe in the direction, want to challenge it, want to contribute, are curious, or may eventually want NIKO. They may also decide not to join. Fine. The waitlist is an access filter, not a conversion trap.

Early production companies, if NIKO reaches production, are likely to emerge from people present during the experiment. Riccardo expects early participants to receive better terms than later general-public customers, but no terms have been decided and this is not a contractual promise.

Someone in the community may see what Riccardo missed. Good. Test it. Learning from another person or system does not diminish founder execution, and founder origin does not make an idea correct. Ten people may disagree with him. Good. Test alternatives. Everyone may agree and still be wrong.

Build open source? Send us the project.

Ernesta Labs publishes its research openly. If you maintain or build an open-source project and want us to examine it, submit it.

We will research it and publish our analysis or opinion for free.

This is not a route to paid praise. There is no payment for positive coverage and no guarantee that our conclusion will be flattering. We will say what we actually think.

First act. Then talk from evidence.

This article does not contain a pricing page disguised as a thesis. It does not design contracts for customers who cannot yet buy the product. It does not invent a complete liability regime, community constitution, or client-admission bureaucracy.

• Exact commission, base amount, resource pricing, packages, and terms are undecided.
• Client admission details are undecided beyond the current B2B and harmful-product boundary.
• Plugin pricing and which specialist resources customers fund are undecided.
• Production transparency views and customer controls are intended, not yet demonstrated.
• Shared learning mechanisms must prove privacy and validation before deployment.
• The private community platform and operating format are undecided.
• NIKO's ability to perform the professional service remains unproven.

Ideas are cheap until acted upon and tested. Founder origin does not make an idea true. Community agreement does not make it true. AI fluency does not make it true.

Execution and evidence determine what survives.

We have said what we think. Now we have to prove it.

Experiment Zero is public. If we are wrong, you will be able to see why. If we are right, you will be able to see how.

You do not have to believe us.

This thesis is based on the completed founder interview and the public Experiment Zero record. Current state is drawn from the public status snapshot and may change. Future product and economic statements are explicitly framed as intentions, expectations, or open decisions.

Primary public record: Watch Experiment Zero, NIKO's Diary, status JSON, and Ernesta Labs Research.