Services

Software and automation for your actual workday.

Good software makes a specific task in your daily business noticeably easier. Nori Works builds small systems, custom tools, and manageable automations you can put into real work early and judge for yourself.

Work areas

The right fit for your workflow.

Sometimes a focused custom application is the answer. Other times, an automated background process saves hours. And often, simply organizing the steps brings the clarity you need.

Build

Internal tools & lean SaaS products

Custom software for your core tasks: clear dashboards, internal tools, and focused web utilities.

What it is

Compact applications solve problems where off-the-shelf software is too rigid. A tool handles your weekly data aggregation, a dashboard displays the status of active cases, or a small helper utility simplifies your work. We focus purely on a stable, usable core.

Who it’s for

If a spreadsheet, a manual workaround, or an improvised process has become too critical for your team to run on gut feeling, a dedicated tool is worth building. This applies to small teams and solo founders alike.

Useful outcomes

  • A usable tool instead of a vague idea
  • Less spreadsheet and copy-paste work
  • Clear status for cases, customers, or tasks
  • A small SaaS start that real users can try
  • A local tool for recurring work

Examples

How it starts

We map the specific problem and define the smallest functional scope that provides real value. Based on this, we build a prototype quickly.

Automate

AI workflows & automation with approval

Automation of repetitive screen work. The system organizes inputs and prepares drafts, while you maintain full control.

What it is

We connect your existing tools into a seamless process. Incoming emails are sorted, details from PDFs are extracted, and matching replies are drafted. This eliminates manual copy-pasting, while keeping critical actions behind a manual approval step.

Who it’s for

This setup assists teams handling recurring invoices, standard forms, or customer enquiries every day. It is especially useful when incoming data arrives via multiple channels and requires sorting.

Useful outcomes

  • Inputs from email, forms, or tools in one place
  • Drafts, summaries, and review packets ready to go
  • Clear approval points for sensitive actions
  • Traceable logs instead of invisible automation
  • Fewer things falling through the cracks

Examples

How it starts

We examine one specific workflow, isolate the routine steps from the decision points, and build a clean automated version for them.

Structure

Process clarity, implementation & handover

Structuring unclear workflows. We organize the steps, implement the appropriate tool, and hand it over to your team.

What it is

Technical clarification comes before clear code. Together, we define who needs which details, where exceptions occur, and where manual sign-offs are necessary. The result is a documented workflow and implementation plan or a focused first solution. General strategy workshops detached from concrete implementation are not part of the offer.

Who it’s for

For businesses that need a practical decision on whether automation, a custom tool, AI support, or a simpler change is the right next step.

Useful outcomes

  • A clear workflow map with decisions and exceptions
  • A first working workflow or prototype
  • Tools, rules, and approval points set up
  • Documentation that actually helps day to day
  • A handover where your team knows what is happening

Examples

How it starts

We start with the specific process that causes the most mistakes or delays today. This yields a straightforward recommendation: build, simplify, or keep manual.

Decision helper

Starting exactly where it makes sense for you.

The right solution depends on your specific bottleneck. Simple automation moves data smoothly, a custom tool brings scattered info together, and AI supports drafting and research.

01

Automation

fits when steps repeat in a similar way and information needs to move more cleanly.

02

Internal tool

fits when spreadsheets, lists, or inboxes have become too important and a clear working view is missing.

03

AI assistance

fits when text, documents, or follow-ups should be prepared while decisions stay with people.

Explore further

Common starting points in more detail.

01

Office workflows for trades businesses

When enquiries, job-site information, quotes, and job status need to connect around existing trade software.

Automation for trades 02

Introducing AI into operations

When AI should prepare email, documents, or knowledge while data routes, limits, and approvals stay explicit.

AI automation for business 03

Technical AI consulting with a workflow and implementation plan

For businesses that need to select a useful AI use case, review data and systems, and define a concrete first functional scope.

AI consulting for business

Offers

From tool check to implementation.

There are two paid starting points. The AI Tool Check determines whether existing products can handle one tightly bounded area of work. The AI Workflow Sprint designs the workflow when handovers, exceptions, or multiple systems need to be resolved first. Either can lead to implementation, but neither commits you to it. All stated prices are net B2B guide prices, excluding applicable VAT.

01

Free first assessment

We take a look at your process and tell you honestly whether and how to move forward.

Have your workflow checked
Guide price
free
Typical path
a short description through the website or by email
Best fit
when you first want to know whether the workflow is suitable at all

What you get

  • a short read on your process
  • an honest assessment: build, clarify, or leave it alone
  • a suggested next useful step
02

AI Tool Check

For one clearly bounded area of work, you receive three to five researched tool recommendations with effort, limits, and a practical adoption plan.

Directories are used for discovery only. Recommendations are checked against current official vendor sources before handover. If no product meets the must-have criteria, you receive a reasoned no-tool conclusion instead of a padded list. If the need spans systems, important exceptions, or custom logic, we recommend the AI Workflow Sprint or implementation instead.

Request a Tool Check
Guide price
990 EUR
Typical path
interview, current research, report, and personal review call
Best fit
when an existing product is likely enough and custom software is not yet needed

What you get

  • a 45-minute interview covering outcome, volume, current tools, data, and exceptions
  • three to five suitable products with cost range, setup, integrations, privacy questions, export path, and limitations
  • one reasoned rejected alternative per recommendation instead of a generic link list
  • an impact-effort matrix, immediate improvements, and a four-part adoption plan
  • a personal review call and an adoption check after roughly 30 days
03

AI Workflow Sprint

A defensible basis for a decision in the form of a workflow and implementation plan, from the real day-to-day process to the smallest useful system scope.

The sprint does not commit you to a follow-up implementation. If you place that order within 60 days, 50 percent of the sprint fee is credited toward the project.

Request a Workflow Sprint View a sample excerpt
Guide price
1,000-2,500 EUR
Typical path
usually a few sessions plus review of real examples
Best fit
when handovers, exceptions, approvals, or multiple systems need to be resolved before a clean build

What you get

  • current workflow with people, tools, handovers, exceptions, and missing information
  • future workflow with deterministic rules, bounded AI, and human decisions
  • a clear recommendation: improve an existing tool, connect existing systems, build a focused solution, clarify first, or deliberately not automate
  • typical, difficult, and high-risk evaluation cases
  • measurable success criterion and smallest useful system scope
  • sequence, timeline, budget, and open risks
04

Automation sprint

One workflow goes live, e.g. request triage or a simple status view.

Request a sprint
Guide price
2,500-8,000 EUR
Typical path
typically one clearly scoped project block
Best fit
when one concrete workflow is known and a small first version may be enough

What you get

  • one usable first workflow
  • setup of the needed rules, views, or integrations
  • documentation and handover for daily use
05

Operational workflow

A larger internal tool spanning multiple roles, data sources, or systems.

Discuss a project
Guide price
8,000-25,000 EUR
Typical path
typically several weeks, depending on scope and integrations
Best fit
when several people, data sources, or existing systems are involved

What you get

  • internal workflow or small tool for daily operations
  • roles, status, approvals, and data flows
  • clean handover with understandable documentation
06

Support & improvement

Optional ongoing support, small adjustments, and improvements once everything is running.

Support stays optional. Documentation and access are handed over so your business is not dependent on an ongoing engagement.

Request support
Guide price
350-2,500 EUR/mo.
Typical path
monthly, depending on need and agreed scope
Best fit
when a system is used in daily work and should keep running cleanly

What you get

  • small adjustments as daily work changes
  • reviewing failed and escalated cases together
  • keeping rules, test cases, and documentation current
  • watching reliability, latency, and cost, including model or provider changes

Workflows

Typical starts.

No invented client stories. These are typical workflows where a small first version can quickly show whether automation helps.

01

Enquiry triage

Problem
Requests arrive by email, form, or message and stay unclear.
First system
One inbox gathers them, spots missing details, and prepares follow-up questions.
Approval
You review before anything is sent to the customer.
Result
Fewer loose ends and a visible status for each enquiry.
See example
02

PDF and document processing

Problem
Attachments, invoices, or documents need to be found, renamed, and copied over.
First system
The system sorts files, extracts relevant fields, and creates a review suggestion.
Approval
You confirm what is accepted, stored, or passed on.
Result
Documents land in a cleaner structure where the next step happens.
See example
03

Quote and follow-up preparation

Problem
Similar requests require searching for texts, prices, and old templates again.
First system
A draft bundles customer details, open questions, and suitable text blocks.
Approval
You decide on content, price, and sending.
Result
Follow-ups and quotes start cleaner without being blindly automated.
See example
04

Status dashboard

Problem
Nobody can clearly see which cases are open, reviewed, or done.
First system
A dashboard shows status, missing details, ownership, and next steps.
Approval
The team sets the final status or approves the next action.
Result
One shared view of work that used to live in lists and inboxes.
See example

Control

Data, approval, and operation

Before drafting any code, we define precisely which systems exchange data, which services are linked, and where manual approval steps are integrated.

Local or cloud

Depending on the project, processing can run locally, inside existing systems, or through suitable services. That is defined upfront.

Approval stays visible

Critical actions like sending invoices or deleting records always remain under your manual sign-off.

Handover over dependency

The first version is documented and handed over so your team understands it in daily use.

Clear limits

Professional review remains in your hands. The software extracts and structures your records, but it is no substitute for your tax advisor or legal counsel.

Read the FAQ View privacy

How we work

How a workflow becomes a system.

The real workflow decides the technology, never the other way around. You show me what actually happens, including the awkward cases, and we build a small first version that can be tested in real work.

  1. 01

    Understand

    We observe the workflow, people, tools, handovers, volume, and recurring exceptions.

  2. 02

    Design

    We define the future flow, deterministic rules, AI boundaries, responsibilities, approvals, and success criteria.

  3. 03

    Build

    I implement the smallest useful production-capable version around the systems already in use.

  4. 04

    Evaluate

    We compare expected and actual behavior across normal, incomplete, difficult, and high-risk cases.

  5. 05

    Roll out and improve

    The system starts in a controlled mode, is observed and documented, and gains responsibility only when the evidence supports it.

Before daily use

A dependable workflow handles the difficult case.

Before a system goes into daily work, we walk through the cases that are rare and still happen. A correct answer matters, and so does a clean stop.

  1. 01

    Missing information

    The system invents nothing. It flags the gap or prepares a precise follow-up.

  2. 02

    Exceptions and failures

    Contradictions, duplicates, and technical failures stay visible instead of passing silently.

  3. 03

    Consequential steps

    Sending, pricing, paying, and deleting need explicit approval. When it gets unclear, a named person receives the case with the context.

Ready to start

What we need for the first step.

You do not need a finished specification. One workflow, one person who knows it, and a few real examples are enough to begin.

  1. 01

    One workflow

    The process that currently costs time, causes mistakes, or needs repeated follow-up.

  2. 02

    One contact person

    Someone who knows the day-to-day work and can point to where it actually gets stuck.

  3. 03

    Three to five examples

    Real emails, documents, spreadsheets, or cases, anonymized where needed and without sensitive data.

  4. 04

    Current tools

    Which systems are in use today. Access only where it is actually needed for the first version.

Boundaries

What to expect and what not to.

  • Consequential or financially risky decisions remain with a named person.

    Instead: The software assembles the available information and open questions for review and approval.

  • Legal, tax, and accounting responsibility remains with your business and its appointed advisers.

    Instead: Logs and documentation make data paths and system decisions traceable.

  • Nori Works is deliberately small. Some specialist questions require additional expertise.

    Instead: You work directly with the person who scopes and builds. Relevant specialists are added when the scope requires them.

  • The first step does not restructure the whole business at once.

    Instead: It is scoped so its usefulness, limits, and effort can be evaluated in daily work.

Assessment