EntridaTechnology & Consulting
Call

Method

The start is free: a 15-minute call or the 3-minute readiness check. Then the paid System X-ray, followed by the build and maintenance. Every step has its scope and its output in writing.

  1. 3working days

    System X-ray

    We start from your diagnostic result and read the process on site: which step touches how many people, where the data breaks, which single flow saves the most money. Your needs become a written scope here, and the build price comes from that scope.

    • A 90-minute working session
    • Process map and break points
    • The scope of the one flow to be built
    • Tool selection and the monthly tool cost
    • A fixed build price and a schedule

  2. 3 to 8weeks depending on scope

    Build

    We build one process or one product in full. The tier is set during the X-ray: S is a single flow, M a multi-tool integration, L several connected flows or a product from scratch. Fixed price, no hourly rate.

    • Build and integration
    • Testing and go-live
    • Team training
    • Documentation
    • A maintenance tier is required after handover

  3. Part of the build contract

    Maintenance

    Automation without maintenance soon stops working. We do not want our name on a system that no longer runs, so we do not sell a build without a maintenance tier.

    • Hosting and release management
    • Monitoring and incident response
    • Flow changes, one request a month
    • A one-page monthly operating report
    • Tracking changes in tool costs

What S, M and L mean: example scenarios

The tier shows how complex the work is: how many systems get connected, how many flows share the same data. Your tier is set during the System X-ray. The scenarios below are real build patterns, and the scope is still written around your own process.

One input, one transformation, one output

Tier measure: 1 to 2 systems · A handful of conditions · A single owner

The four measures that set the tier

Number of systems
How many separate tools the flow touches: email, ERP, accounting, spreadsheets, CRM, the carrier panel.
Number of decisions
How many conditions and exceptions sit inside the flow: approval steps, thresholds, splits by country or product.
Data transformation
How much one system's output has to be cleaned and mapped before it can enter the next one.
Ownership load
How many people's daily work changes, and how many need training and access rights defined.

  • Accounting entry from an incoming invoice

    Trigger

    A supplier invoice arrives by email

    Flow

    1. Vendor, date, amount, VAT and line items are read out of the PDF
    2. Field names are mapped to the chart of accounts
    3. The entry is written to accounting as a draft and goes for approval

    Result

    Approval is the only step left by hand

    Systems it touches

    Email · OCR · Accounting

  • Letter of credit condition checklist

    Trigger

    The bank sends the letter of credit text

    Flow

    1. The conditions in the text are broken out one by one
    2. Each condition gets an owner and a deadline
    3. The list is handed out to the right people as tasks

    Result

    An impossible condition is visible on day one

    Systems it touches

    Documents · Task management

  • Follow-up chain after a quote

    Trigger

    A quote is marked as sent

    Flow

    1. Reminders are set for day 3, day 7 and day 14
    2. The chain stops on its own as soon as a reply comes in

    Result

    No quote is left without follow-up

    Systems it touches

    CRM · Email

The tier shows scope. The final figure is written as one number at the end of the System X-ray.

Process

  1. Readiness check

    We start with the free tool. We measure where you stand.

  2. System X-ray

    We write what will be built, what will not be built, and what it costs.

  3. Build

    One process, from start to finish, fixed scope.

  4. Handover and maintenance

    Your team starts using it. We host it, watch it, fix what breaks and update the flow as your needs change.

What we settle before starting

  • Someone inside the company is named as the owner of the system, because an unowned system gets abandoned.

  • One process at a time: we finish one, then move on to the next.

  • If the data lives on paper and in WhatsApp, we set up a single source of record first. The build starts after that.

Book a call

The first call is 15 minutes and free. The calendar, email and address are on the Contact page. Note the process you want to discuss when you book.

Book a call