Skip to content
Samer Hany

Expert Process & Calculation Systems

Turn a specialist method, calculation, or report into software other people can use without losing the logic that makes it valuable.

Businesses whose most valuable work depends on a method only a few people fully understand, and which has become slow, fragile, or impossible to hand to a customer.

From expert method to dependable software

  1. 01

    Existing method

    Files, formulas, judgment, and exceptions

    then
  2. 02

    Explicit logic

    Rules inventoried and edge cases resolved

    then
  3. 03

    Tested system

    Application logic checked against real history

    then
  4. 04

    Usable result

    A controlled tool other people can rely on

The interface is only the visible layer. The valuable work is making the rules explicit, proving the output, and preserving business control.

Solutions

Common starting points

  • A complex spreadsheet full of formulas, macros, validation, and business rules
  • A manual engineering or consulting methodology
  • An expert moving between several applications to produce one result
  • A process built from documents, templates, and repeated report preparation
  • Technical knowledge held mainly by one experienced employee
  • A manual estimating, assessment, configuration, pricing, or quoting process

You may recognize this if

  • One or two people are the only ones who genuinely understand how the numbers are produced.
  • Producing a quote, estimate, or report takes hours of expert time that could be spent elsewhere.
  • You would like customers to serve themselves, but you cannot hand them the working file.
  • Nobody wants to change the logic because nobody is confident what else it would affect.
  • The method is a genuine competitive advantage and it is sitting somewhere fragile.

What you end up with

  • The calculation runs in seconds, with the same answers as before.
  • Expert time moves from producing outputs to reviewing them.
  • The logic is documented, tested, and no longer dependent on one person.
  • Customers or field staff can use it directly where that makes sense.
  • The method becomes something you can price, license, or productize.

Usually delivered as

  • Web application

    A place for your team, an expert, an administrator, or your customers to do the work.

  • Automated system

    Background software that connects tools, moves information, and keeps the process running.

  • AI agents

    Agents that interpret information, use tools, and handle clearly defined tasks, standalone or inside another system.

Most projects combine at least two. I will recommend the right mix after I understand the process.

A real example

Custom windows and doors manufacturing · Australia

Producing a single customer quote took two to three hours and passed through four separate people or systems, each one a chance to mistype a number that the whole price depended on.

2 to 3 hours ~10 minutes

How I approach it

Understand the method before touching software

I work through how the result is actually produced, including the exceptions and the judgment calls that never made it into any document. That is usually where the real logic lives.

Inventory every rule

Formulas, lookups, macros, validation, and the rules that exist only in someone's head get written down and confirmed. Anything ambiguous is resolved before it becomes code.

Prove parity before improving anything

The new engine runs against real historical cases and its output is compared to the original until they agree. A system that is cleaner but produces different answers is worse than no system.

Design for the people who actually use it

A field technician on a tablet and an analyst at a desk need different things. The interface follows the real working conditions, not the shape of the data.

Keep the business in control of its own rules

Rates and pricing logic stay editable. Hard-coding them would trade a file you control for software you have to call someone about.

What is included

  • A working application with the calculation logic reproduced and tested against your originals.
  • Parity testing on real historical cases, so the numbers are provably unchanged.
  • Role-based access separating who can use, review, and change the logic.
  • Generated documents and reports where the process produces them.
  • Admin control over rates and rules, so the business keeps ownership of its own logic.

Investment

Implementation

$20,000 to $50,000

Projects start at $10,000 and most land in this range. Cost moves with scope, integrations, and how much of the existing logic is documented.

Solution Blueprint

$1,500 to $3,000

Scope, architecture, risks, and a phased plan. Credited toward implementation when work starts within 30 days.

If the path is clear, we can go straight to implementation. If it is not, the Blueprint is the cheaper way to find out what you are actually buying.

What partners say about this kind of work

Samer was the only one who truly took a deep dive into the process we were hoping to automate. He studied the files and asked questions that showed he fully grasped every detail.

Victor G.

That demanded different kind of skills in programming, math, design, creative thinking and problem solution. He excelled in all of them.

Joao

Describe your version of this.

No specification needed. A plain description of how the work gets done today is the most useful thing you can send.

Describe your process