Services

Software and automation for your actual workday.

Nori Works builds small systems, internal tools, and AI-assisted workflows. Not as a concept deck, but as a working first version you can put to use.

Service fields

Build, automate, structure.

Sometimes the right step is a dedicated tool. Sometimes it is an automated workflow. Sometimes the process needs structure first.

Build

Internal tools & lean SaaS products

Small software for specific jobs: internal tools, dashboards, local-first utilities, and lean SaaS products.

What it is

We build compact systems around one clear problem. A tool that replaces spreadsheet work, a dashboard that shows where a process stands, a small product that turns an idea into something usable. The aim is not maximum feature depth but a clean first version that people actually open every day.

Who it’s for

For businesses, freelancers, and teams with a concrete idea or a task that keeps eating time. When a spreadsheet, a manual ritual, or a half-working workflow has become too important to ignore, a dedicated tool is worth building.

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

  • Quote or order overview
  • Dashboard for process and customer status
  • Local-first tool for private or sensitive data
  • Lean SaaS product for a focused audience

How it starts

We clarify the problem, the desired outcome, and the smallest scope that makes sense. Then we build a first usable version, not a grand concept.

Automate

AI workflows & automation with approval

Recurring work gets prepared, sorted, or kicked off. Critical steps stay visible and need your sign-off.

What it is

We connect the tools you already use and turn recurring screen work into a clear workflow. Inputs are gathered, information is prepared, drafts are created, and status becomes visible. Anything that involves sending, deleting, paying, or making a binding decision keeps a human in the loop.

Who it’s for

For teams that handle similar emails, documents, invoices, or handovers every day. Especially useful when work starts in several places and nobody can see clearly what is already done.

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

  • Inbox triage with prepared follow-up questions
  • Document or invoice review with approval
  • CRM or spreadsheet sync without double entry
  • Agent workflow with log, status, and stop sign

How it starts

We pick one concrete workflow, mark the repetitions, risks, and decision points, and build the first clean version from there.

Structure

Process clarity, implementation & handover

When the workflow is still fuzzy, we bring order: understand it, scope it down, build it, document it, and hand it over.

What it is

Not every process is ready for software right away. Sometimes the steps, roles, exceptions, and approval points need to become visible first. We map the workflow, decide together what should be built, implement a first version, and hand it over so your team can work with it.

Who it’s for

For businesses and freelancers who sense that AI or automation could help but do not want a bloated transformation project. The goal is a sensible next step, not a technology program.

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

  • Process mapping with an automation roadmap
  • Review of an existing workflow
  • Tool setup with documentation and onboarding
  • Improving a workflow that already half works

How it starts

We begin with the workflow that is currently costing time or causing mistakes. From there you get an honest read: build it, simplify it, or consciously leave it alone.

Core offer

Small automation systems

An automation system takes a real workflow and makes it easier: gather inputs, prepare information, create drafts, show status, and stop critical steps for approval.

A fit when

01 enquiries, documents, or tasks start in several places

02 too much work is copied, searched for, or followed up manually

03 a spreadsheet has become important but nobody fully trusts it

04 a tool already exists but the workflow still gets stuck

What gets built

01 one shared inbox or a clear working view

02 prepared follow-ups, summaries, or drafts

03 status that shows what is open, reviewed, or done

04 clear stops before sending, deleting, paying, or approving

01

Where people decide

The system prepares. Binding steps stay visible and need your approval.

02

What is handed over

You receive a usable first version, documentation, and an introduction. The goal is a system your team can run in daily work.

03

How it starts

We take one workflow that currently costs time and cut it down to the smallest useful first version.

Example workflows

Four typical starts.

No invented case studies. 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. Estimate: ~2–3 hrs/week less searching
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. Estimate: ~1–2 hrs/week less manual filing
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. Estimate: ~30–60 min less per quote
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. Estimate: ~1 hr/week less status chasing

Control

Data, approval, and operation

Before anything is built, we clarify which data is processed, which services are involved, and where approval must remain visible.

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

Sending, deleting, paying, or binding decisions do not happen quietly in the background.

Handover over dependency

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

Clear limits

Automation does not replace legal, tax, or accounting review.

Read the FAQ View privacy

Method

How a workflow becomes a system.

The work does not start with a tool name. It starts with the process. We use modern AI tools, local and API-based models, and standard integrations, but the workflow decides which technology fits.

  1. 01

    Understand the workflow

    We map what happens, who is involved, which tools are in play, and where work gets stuck.

  2. 02

    Pick the smallest useful step

    Not everything needs to be in version one. We scope the first version so it ships fast and stays clean.

  3. 03

    Build and test

    We build the system, connect the necessary tools, and test the workflow with real examples.

  4. 04

    Hand over and improve

    You get documentation, clear approval points, and a version that can grow over time.

Boundaries

What to expect and what not to.

  • No fully automatic handling of risky or consequential decisions.

    Instead: The system prepares the decision, you give the approval.

  • No legal, tax, or accounting review.

    Instead: We document clearly enough that your accountant or lawyer can review it quickly.

  • No large agency team and no off-the-shelf enterprise product.

    Instead: A small, founder-led studio that builds exactly the slice you need.

  • No miracles and no automating everything at once.

    Instead: The smallest useful first step, already usable in daily work.

Assessment