Email us

What we build, and what you receive with it.

Five kinds of system. Every engagement follows the same six steps, starting with a specification you approve before we build, and ends with documentation your team can run it from.

Document pipelines

Multi-step AI workflows where every AI step is followed by a check that decides pass or fail.

What you receive

  • Workflows broken into small steps, each with one job and clear inputs.
  • A deterministic check after every AI step, so nothing unchecked reaches a person or another system.
  • Failures that stop and name the problem instead of guessing.
  • Designs that do not depend on one model vendor.

See it in practice: the extractor that may say “missing”.

Answers from your own documents

Search and answers over your SOPs, contracts, manuals and tickets, with the source cited every time.

What you receive

  • Your documents indexed where your data rules allow.
  • Every answer linked to the passage it came from.
  • A plain “not in the documents” instead of an invented answer.
  • A way to check answer quality before and after launch.

Process automation

Robotic process automation in UiPath and n8n for the repetitive work between your systems.

What you receive

  • The process designed on paper first: triggers, systems, failure handling.
  • Automation built module by module, with documentation for each module.
  • Data checked against the system or register that is the source of truth.
  • Maintenance after launch, for as long as you need it.

See it in practice: seven processes for AutoSync.

Records and back-office systems

Invoices, reports, official documents, reminders and archives joined into one system.

What you receive

  • A register of issued documents where nothing issued can be edited, only cancelled and replaced.
  • Reports generated from source data, so a figure is typed once and every document agrees.
  • Official PDFs and forms read into structured data, with a person confirming each field.
  • Reminders driven by rules, sent once and logged, and an archive with checksums and a retention rule.

See it in practice: Kvit, the system that runs our own back office.

Handover and support

Reviews, training and on-call help while your team takes ownership of what we built.

What you receive

  • Code and design reviews against the agreed specification.
  • Training and mentoring for the people who will run the system.
  • Small fixes and changes after launch.
  • A clear end point, when your team no longer needs us.

One path, every engagement

The specification is agreed before anything is built, and everything after is measured against it.

  1. Research

    Your process, your data, where the time goes.

  2. Planning

    Scope, risks and what success is measured by.

  3. Specification

    The requirements and design you approve before we build.

  4. Build and test

    Built module by module and tested against the specification.

  5. Evidence

    Design decisions, test results and module documentation, handed over.

  6. Handover

    Training and support until your team runs it alone.

How an engagement is shaped

Paid discovery

A short, fixed piece of work that ends in a written specification you own, whether or not we build it.

Fixed-scope build

We build what the specification says, for an agreed scope. Changes are written down before they are made.

Support with an end point

Optional monthly support, with a date when your team runs it without us.

We give a price on the first call, once we understand the scope.

Tell us which process takes too long.

Describe the process and where it hurts. An engineer who would work on it replies within one business day with questions, not a sales deck.

Email office@noni-soft.com