Software is eating your business.

A policy change becomes a software project. You pay to build it, wait to use it, then pay to keep it running.

Inferal eliminates the custom software between a business decision and what happens next.

Click or tap to play or pause. Double-click or double-tap to rewind. At the end, the video rewinds and waits for you to play it again.

The cost of changing your business

You already made the decision. Why are you funding another project?

Change a policy. Approve a supplier. Respond to a delayed shipment. Someone turns the decision into tickets, integrations, workflows, and code. Then you pay to keep that translation running. When the business changes, you pay again.

  1. Translation≈ $0Lastshours

    Someone decides what should happen, under which conditions, and why it matters to the business.

    Business contextIntent explicit
  2. Capacity≈ $470/ five-person hour1Lastsdays

    People explain, challenge, and interpret the decision together. Shared context becomes conversation and notes.

    Shared discussionInterpretation begins
  3. Capacity≈ $25–$50/ ticket1Lastsa few hours

    The agreement is compressed into a unit of work: a request, acceptance criteria, and a place in the backlog.

    Work itemIntent summarized
  4. Capacity≈ $3.8K/ developer-week1Lastsmonths

    The request becomes precise enough to implement. Ambiguity narrows, but business rationale starts to fall away.

    Technical contractBehavior defined
  5. Capacity≈ $16K/ developer-month1Lastsmonths
    if (condition.matches(context)) {
      await execute(requiredAction);
    }
    Application logicMeaning encoded
  6. Capacity≈ $49K/ developer-quarter1Lastsyears

    The implementation enters a specific environment with configuration, dependencies, versions, and release constraints.

    Runtime environmentBehavior live
  7. Cost≈ $59K–$85K/ developer-year2Lastsuntil retired

    Software keeps accruing obligations after release. Every change must preserve business intent while the technical world beneath it keeps moving.

    Ongoing systemCost compounds
One business decision. Six handoffs. Then upkeep. AI can write the code faster. You still own what it leaves behind.

How it works

Keep the business rule. Eliminate the software built around it.

State what should happen and under which conditions. Inferal connects those rules to current facts, determines what follows, and sends the result to the people, systems, and agents that act.

The facts change. Your business responds.

Operational teams

Make the decision once.

Define the conditions, exceptions, and response in the terms your team uses. Inferal evaluates the rule as the facts change.

Risk and governance

Keep intent inspectable.

See which policy applied, which facts matched, and why an action followed. Keep the explanation with the outcome.

Engineering

Build what makes you different.

Focus on the algorithms and capabilities unique to your business. Changing an operational rule shouldn't require another application release.

The rule stays explicit. The evidence stays attached.

This is an operational model.

The rules, facts, relationships, and policies you just saw form a live, governed representation of how the business works. Ontologies give that model shared meaning across systems and agents.

Explore operational models

Every outcome keeps its why.

Why?

Decision provenance

Because the rule stays connected to the data it evaluated, every outcome retains the exact instruction, evidence, and moment behind it.

Decision receipt

Record 0142

Delivery exception

A late delivery was caught while there was still time to respond.

What changed

A delivery is now expected late.

The vehicle’s latest position moved the expected arrival from 16:42 to 17:18.

What should happen

Late deliveries require intervention.

If the expected arrival is later than 17:00, open an exception and notify the consignee.

What happened

The exception was opened.

The consignee notification was requested automatically.

Recorded at
14:32:08, when arrival changed to 17:18
Policy in force
Late-delivery response, effective 12 June
Evidence at that moment
Vehicle position at 14:32, arrival 17:18, delivery due 17:00

Where to start

Start with one thing your business should already be able to do.

Choose the scope that solves today's problem. Each starting point has value on its own. Expand when the next step earns its place.

  • Agree on what things mean.

    Start with one domain. Define the customers, commitments, approvals, and policies your systems describe differently. Give your teams and agents definitions they can share.

    Explore Operational Models

  • Answer a question across systems.

    Start with one recurring question. Connect the relevant facts and rules, then show the evidence behind the answer. Use it to support a decision before introducing automated actions.

    Explore the Data Platform

  • Run one changing process.

    Start with a bounded process. Connect its rules to live data and deliver the resulting decisions or actions to the systems your team already uses. Agree on how to measure its value.

    See how the platform acts

Need dependable data first?

Relay keeps data moving between your existing systems and the products, teams, and agents that use it. Start with one integration. It has value on its own, whether or not you add operational models or decision logic.

Explore Relay

What people see in Inferal.

What?

Customer perspectives

“In an era where source code became a commodity, being able to get exactly the data you want in real-time is the moat you need to develop powerful agents. Inferal Relay provides this moat for us.”

“If the data is the source of truth, then business decisions should be made as close to it as possible. Inferal lets you push your business rules right to the data itself.”

Nisan HaramatiCo-Founder at Graphium Labs

“We monitor DNA sequences, protein data, antibody assays, and need to act on new relationships continuously. Inferal executes rules close to the database, giving us a fast way to alert AI agents and researchers.”

Morten KroghCTO at Bionamic

“Clearly the future for rule-based agentic behavior for all verticals. Everyone else is using agents in a reactive way and Inferal is using them proactively.”

Sean MaginSoftware Engineer

“What stands out about Inferal is how directly their approach translates into faster execution and lower complexity.”

Michel PelletierFounder at OneSparse

“The database sees everything going in and out, but it usually just stores it. Inferal turns those changes into instant actions without adding a bunch of extra systems.”

Rob PankowCEO at simplyblock

Find your starting point

Take your business back from software.

The build is only the beginning. Changes, integrations, audits, and upkeep keep the bill growing.

Which scenario fits you best?

  • Sales change. Your ad spend doesn't.

    Campaign budgets, sales, stock, and margin live in separate systems. Your team reconciles reports to decide what to promote, pause, or scale. Every new channel adds more software between a sale and the next advertising decision.

  • A risk policy changes. Approvals stall.

    Your team changes an approval threshold. Onboarding, risk checks, and exception queues need updates in different systems. The policy is agreed; release dates decide when it applies.

  • A player's eligibility changes. Your controls lag.

    Location, identity checks, account limits, and exclusion status live in separate systems. Every rule change means more integration work before your controls can act on the current facts.

  • The referral is ready. The handoff isn't.

    A referral is ready, but eligibility, appointment capacity, and approval status sit in different systems. Staff chase updates while your team maintains the workflow between them.

  • New models. Old architecture. More upkeep.

    Every release adds prompts, agent flows, and code shaped by the model you had then. Those design choices outlive the model. Business rules drift between versions, and your team inherits an expanding system of workarounds to reconcile and maintain.

  • A permit rule changes. The queue doesn't.

    Zoning, inspections, and payments have separate records. A rule change means more software work before staff can apply it consistently to the applications waiting for a decision.

  • One machine stops. The workarounds multiply.

    A line goes down. Production schedules, parts inventory, and maintenance records disagree. Supervisors replan by hand while engineers maintain the scripts between systems.

  • Your recall starts with a spreadsheet.

    A supplier flags a batch. Your team reconciles intake records, warehouse stock, and delivery manifests to find which orders it reached. Each new supplier adds another integration to maintain.

  • Conditions change. Your plan waits.

    Weather, soil readings, equipment availability, and buyer commitments live apart. Field plans change by phone and spreadsheet. Every new crop or operating rule needs another software patch.

Book a 45-minute call

Bring your example. We'll assess fit and explore a possible first step. No commitment.