Fort AI Systems logo

Fort AI Systems

Fort Revenue Recovery

When estimates, jobs, invoices, and payments stop agreeing, revenue gets hard to see.

Not leads you never got. Work you already quoted, that then went quiet somewhere between the estimate and the money — and no longer shows up in any one place clearly enough to chase.

  • CoverageEstimate records only
  • EvidenceSynthetic only
  • Customer resultsNone yet
  • Public priceNot approved

Where the records split

One system says the work was quoted. Another says what was invoiced and paid. When those two stop lining up, the difference is not written down anywhere — it is just the gap between them.

Two business records diverging, then reconcilingAn illustrative diagram with no values. An upper track represents estimate and job records; a lower track represents invoice and payment records. The two begin together, separate across a hatched region labelled reconciliation gap, and close again at a node labelled reconciled.
  • Estimate / job records
  • Invoice / payment records
  • Reconciliation gap
  • Reconciled
The gap between two records is what the Revenue Recovery method is designed to inspect. Validated today for one source: an authorized export of your estimate records. Illustrative structure only — the figure carries no values and does not represent a customer.

Where this actually is today

Worth stating before anything else, because the honest answer is narrower than the idea.

Validated

Built and tested

One detector, for stale estimates. A file boundary that refuses anything it cannot read cleanly. Record-by-record sorting into eligible, excluded, or insufficiently evidenced, with the provenance kept, and eligible pipeline totalled. All of it verified against synthetic test files only. It is not connected to anything, and no real business file has been through it.

Designed

Designed, not built

Examining economic leakage across the other business-system records a company keeps — customer records, estimating and field-service systems, scheduling, email, accounting and invoicing — as each source and workflow is validated in turn. None of that runs today. It is written down as a method so it can be judged, not sold as a capability.

Who this is aimed at

Working hypothesis

This is a stated guess about who the work suits, not a validated segment. No business has been through it, so nothing below is drawn from experience with a customer.

Likely a fit

  • Enough estimate volume, at enough value per job, that a missed one actually matters.
  • Estimates, jobs, invoices, and payments living in more than one place.
  • Nobody whose job is to reconcile them against each other.
  • An owner or manager who can authorise an export of their own records, and act on what it says.

Not a fit

  • Anyone wanting more leads. This looks at opportunities you already had.
  • Anyone wanting the work done for them automatically — nothing here acts on your behalf.
  • A business whose records are already reconciled. There would be nothing to find.
  • Anyone who needs a guaranteed number. No outcome is promised, and none has been measured.

How it works, and how far it is proven

Every step carries its own state. 3 of the 6 are built; the rest describe where the method is going.

  1. 01Find leakageValidatedToday this means stale estimates inside an authorized export of your estimate records.
  2. 02Show evidenceValidatedWhy each record is eligible, excluded, or insufficiently evidenced — with its provenance kept.
  3. 03Audit what you ownDesignedWhether the systems you already run adequately cover the finding.
  4. 04Recommend the cheapest sufficient fixDesignedConfiguration before anything new is proposed.
  5. 05Observe what happened nextDesignedFrom evidence you authorize and provide. Nothing about your business is monitored automatically.
  6. 06Quantify eligible pipelineValidatedOnly eligible pipeline. Booked, invoiced, collected, and incremental value belong to the designed method, not to what is built.

The method can conclude that your existing software already covers it, or only needs configuring. That is a complete result, not a failed sale. Another reminder sequence is not the point.

What comes back

No frequencies implied

A Revenue Recovery Scan returns a written result, record by record, where every line says what was found and how well it is supported. Each record lands on one of these conclusions.

  • High-confidence actionable leakage

    Validated

    The records line up, the rule is met, and the opportunity is worth putting in front of you.

  • Medium-confidence opportunity

    Validated

    Something is there, but the evidence is thinner. Labelled as such rather than promoted.

  • Insufficient or conflicting evidence

    Validated

    The records disagree, or the link is missing. Reported as a result — never filled in with a guess.

  • Your existing system already covers it

    Designed

    A complete answer. The Scan says so and stops, and nothing is recommended.

  • A cross-system gap worth Fort's involvement

    Designed

    Only where a real gap remains after the systems you already run have been checked.

  • Action taken, and what happened after

    Designed

    Recorded from evidence you provide. Nothing about your business is watched automatically.

This is the list of conclusions a record can reach. It is not a breakdown of how often each one happens — that has not been measured, and no share, rate, or likelihood is claimed anywhere on this page.

How a number earns the right to be shown

The reason to trust a figure is not that it is large. It is that you can see what it is made of, what state it is in, and what is not being claimed about it.

Anatomy of one finding

Illustrative structure · no values
Opportunity category
Face value1
Economic state2
Evidence confidence
Opportunity age band
Attribution basis4
Native-system result3
Source system / lineage
Calculation version
As-of date1
  1. 1Every amount carries its currency, time range, and as-of date. A number without them is not a finding.
  2. 2States are never collapsed. Eligible is not booked, booked is not invoiced, invoiced is not collected, and estimated is not verified.
  3. 3“Your existing system already covers this” is a complete and valid result. Fort is not required for a finding to be resolved.
  4. 4Economic state, evidence quality, and attribution are recorded separately. A collected amount with no defensible attribution is still a collected amount — it is just not Fort's claim.

Three separate questions

What happened economically, how well it is evidenced, and what may be said about Fort’s part in it are three different questions. They are recorded separately, answered separately, and never merged — so a collected amount with no defensible attribution stays exactly that.

Economic state · what happened

  1. 01Eligible / potential opportunityMeets the detector rules and is awaiting action or outcome. Never labelled recovered.
  2. 02BookedLinked acceptance or job evidence exists. An observed business outcome, not automatically Fort-caused.
  3. 03InvoicedA linked invoice was issued. Kept separate from collected cash.
  4. 04CollectedPayment was settled under the approved evidence policy. Never inferred from an invoice status alone.

Evidence quality · how well supported

  • VerifiedThe finding is supported at the stated evidence level. This describes the evidence, not the economics and not Fort's contribution.
  • EstimatedModelled rather than observed. Method, assumptions, and uncertainty are stated alongside it.
  • Insufficient evidenceA first-class result, not an error. The record is shown as insufficient rather than quietly dropped.

Attribution · what may be said about Fort’s part

  • Influenced / assistedFort activity was observed alongside the outcome. Co-occurrence only — this is not a causal claim.
  • Estimated incrementalA modelled difference from business as usual, labelled with its method, assumptions, and uncertainty.
  • Verified incrementalNot available yetAn effect supported by a defensible comparison. Defined here for completeness only.
  • Not establishedNo defensible attribution claim exists. The economic outcome may still be real and fully evidenced.

No frequency, rate, or likelihood is implied by any of these lists. They are vocabularies, not measurements.

How an opportunity is realised

Illustrative structure · no values
  1. 01

    Eligible / potential opportunity

    Requires
    Meets the detector rules.

  2. 02

    Booked

    Requires
    Linked acceptance or job evidence exists.

  3. 03

    Invoiced

    Requires
    A linked invoice was issued.

  4. 04

    Collected

    Requires
    Payment settled under the approved evidence policy.

Records can stop at any stage, and many never advance at all. Every segment above is drawn the same size on purpose — nothing here says how many advance, how fast, or why.

Advancing is a business outcome, not evidence that Fort caused it. What may be said about Fort’s part is a separate question, answered on the attribution axis.

Each stage carries its own evidence. A record can be collected and still be poorly evidenced, or well evidenced and never advance.

What a finding can conclude

Illustrative structure · no values

Listed cheapest first, because the cheapest sufficient fix is the one worth having. Two of these four conclusions end with Fort recommending nothing.

  1. Your existing system is sufficient

    Preferred outcome

    The workflow you already pay for adequately covers the finding. The Scan says so and stops there.

    Costs you · Nothing new to buy, and nothing to change.

  2. Configuration is sufficient

    Preferred outcome

    An available feature, setting, or ordinary process correction covers it. No competing Fort automation is justified.

    Costs you · A change to something you already run.

  3. Fort involvement may be justified

    A useful evidence or reconciliation gap remains after native configuration has been tested — not before.

    Costs you · A bounded piece of work, agreed separately.

  4. Insufficient evidence to conclude

    The available records do not support a conclusion. This is reported as the result rather than resolved by assumption.

    Costs you · More evidence, before any recommendation.

These are the conclusions a finding can reach — not a distribution. No frequency, share, or likelihood is implied, and none has been measured.

What it does not do, and what it never touches

Where the data comes from

Eventually, an export of your own records — one you authorize and provide deliberately. Nothing is pulled from your systems and there is no connection to them. Reading this page or writing to us moves no data and processes nothing.

Do not send records, exports, credentials, or system access by ordinary email — not to us, not to anyone. There is no upload on this page and no account to create. If a transfer is ever appropriate, we explain what is required and how it would be handled, and you authorize it explicitly, before anything moves.

Boundaries

No customer of yours is contacted. Nothing is automated on your behalf. No guarantee, no promised recovery, and no financial claim is made. Any future step would need your explicit authority first.

Revenue Recovery is the broader recovery family and method. Lead Recovery is the bounded module available today, with its own separate offer. It does not implement this method, and most of it is not available through Lead Recovery.

The questions worth asking first

Can I use this today?
You can ask to take part today — that is what the request button does, and it sends an ordinary email. What you cannot do yet is run a Scan yourself: there is no self-service upload, the detection logic has only ever run against synthetic test data, and no real business file has been through it. Asking is open; the analysis is still being validated.
Is this just another reminder tool?
No, and the difference is what happens when your existing setup is already adequate. A reminder tool adds another sequence regardless. This checks the systems you already run first, and will conclude that they cover it if they do.
What would you need from me?
Eventually, an export of your own estimate records — one you authorise and hand over deliberately. Not yet, though, and not by email: please do not attach customer records, exports, credentials, or system access to your first message. That first email is a conversation. If it goes further, we explain exactly what is needed and how it would be handled before you authorise anything.
My records are messy. Does that break it?
Messy records are the normal case. Where two sources disagree or a link is missing, that record is reported as insufficient evidence rather than being filled in with an assumption. A thin answer you can trust beats a confident one you cannot.
Will you contact my customers?
No. Nothing here contacts anyone, sends anything, or acts on your behalf. Any future step would need your explicit authority first.
What does it cost?
No price has been set. This page will not quote you one, and nothing on it is for sale. Asking costs nothing and commits you to nothing.
How is this different from Lead Recovery?
Lead Recovery is the bounded module that is actually available today, and it deals with inquiries that never got captured. Revenue Recovery is the broader method, looking at opportunities you already captured that then stopped agreeing across your systems. Most of the broader method is not available through Lead Recovery.
What happens if you find nothing?
Then that is the result, and you have a reconciled picture and a reason to stop worrying about it. Finding nothing is a legitimate outcome, not a failed engagement.

Early validation

If your estimates and your money have stopped agreeing, say so.

A short email is enough. Tell us roughly what you run and where you think things are slipping, and we will tell you honestly whether this is worth either of our time yet.

Request a Revenue Recovery Scan

Opens your email app · nothing is sent until you send it

  • This is early validation. Nothing has run for a customer yet, and no finding is guaranteed.
  • Please do not attach customer records or exports to your first email. Ordinary email is not the place for them.
  • The first message is only a conversation. No data moves and nothing is processed because you write to us.
  • If it goes further, we explain first. What information is required and how it would be handled, before you authorise anything.

The request goes to sales@fortaisystems.com. There is no form on this page, no upload, and no account to create.

Illustrative structure only · no customer data · no customer outcome · no measured frequencies · no guaranteed finding · Revenue Recovery Scan has not yet run for a customer