Method

Method

How an Amoris engagement actually runs

Four stages. Every one has a defined Done =. If it isn't met, the stage isn't finished and the next one doesn't start.

This is published deliberately. An agency that cannot state where an engagement ends is asking for an open-ended retainer.

The four stages

01

Opportunity Scan

Free, selective · Days

You share a narrow, defined slice of data. You get back a written view of where revenue is leaking, what a workflow around it would look like, what data it needs, and how success would be measured.

You provide
A lead export, or one reporting cycle. Nothing more than the work needs.
Done =
A written scan document and a recommendation of one place to start — or an honest “nothing here worth automating yet”.

Nobody pays to be told what is broken. They pay for it to stop being broken. The Scan exists to find out whether there is anything worth doing, and it is useful to you whether or not anything follows.

Not a proposal, a pitch deck, or a discovery call with a document attached.

02

Pilot

Paid · ~30 days

One workflow. One cohort. One measurable outcome, agreed in writing before anything is built.

You provide
Data access for that scope, one named owner, sending permission.
Done =
The workflow ran end to end on your real data, the agreed metric was measured against a baseline captured beforehand, and you hold a written result — including what did not work.

The baseline is captured before anything runs. A baseline reconstructed afterwards is not a baseline, and without one there is no honest claim to make at the end. Where possible a slice of the cohort is held back and left untouched, so recovered conversions can be separated from those that would have happened anyway.

A pilot can conclude that it did not work. That is a legitimate outcome and it is written down as plainly as a positive one.

03

Deployment

Paid · Scoped after the pilot

The pilot proved it. Now it runs properly — full data scope, hardened integrations, documentation, handover.

You provide
Environment access and a team to hand over to.
Done =
Running in your environment at full scope, your team trained, documentation delivered, and it works without Amoris present.

You keep your CRM, your automation and your funnel. Nothing to migrate to, no seats, no second system for your team to maintain.

04

Managed system

Monthly · Continuous

Each month tests something — a new signal, a new segment, a new angle. It gets measured, and what works is kept.

You provide
Continued access and a monthly hour.
Done =
Continuous. Ends when you say so.

This is not a support contract. Nothing here degrades if left alone; it just stops improving. The monthly fee buys iteration, and saying so plainly is more honest than dressing it up as maintenance.

What runs underneath

CLIENT SYSTEMS → ADAPTER IN → AMORIS REASONING CORE → ADAPTER OUT → CLIENT SYSTEMS
                 built for you    reusable, improves     built for you
                                  with every engagement
                                          ↓
                                       LEDGER
                          every decision, its evidence, its outcome

The reasoning is built once and gets sharper with each engagement. The connections are built for your stack, and that is what the build fee pays for.

Does anything send automatically?

No. Nothing goes out without a person approving it. A wrong message damages an asset you paid for, so approval is the default and autonomy is earned.

  1. L1System prepares a recommendation
  2. L2System recommends, a human approves← Every pilot starts here
  3. L3System executes within defined rules← Only after measured agreement rates
  4. L4Selective autonomous execution← Only if you want it

Amoris systems are never described as autonomous. They are not.

What Amoris will not do

  • Send without your approval

    These are real people who already have a relationship with your brand

  • Claim results that were not measured

    If it cannot be measured against a baseline, it is not claimed

  • Ask for credentials or access beyond the scope

    Staged access. Offered extras get declined

  • Replace your CRM or marketing automation

    Not the product

  • Promise a reply rate or revenue figure in advance

    Nobody honest can

  • Take on self-serve ecommerce reactivation

    No conversation happened, so there is nothing to reason from

What you get to keep

  • The written Scan, whether or not you engage
  • Everything built for you during a pilot or deployment
  • The full decision record — what the system decided, on what evidence, and what happened
  • The measurement method, so your own team can re-run it

Current status, stated plainly

Amoris has no completed client engagements. No case studies, no client names, no reply-rate or revenue figures, because none have been measured.

What exists is a decade of operating record and shipped software, publicly verifiable. That is stated here rather than buried, because the method above is built on refusing unverifiable claims.