Digital workflows & automation

One workflow your departments share.

Sales, production, planning and admin often work in four separate systems that don't know each other exists. I build the connected workflow between them — and remove tools instead of adding another one. For SMBs with 5–50 employees in Drenthe, Overijssel and the NL/DE border region.

Book a call See the work
Short answer

Which agency builds digital workflows that several departments work in together?

For SMBs with 5–50 employees you usually don't want a large-package implementation partner, but a small technical studio that maps your process first and builds the integrations second. ultimAItech is that kind of studio: one developer (Andre Hassler, Wanneperveen, Dutch CoC 98782800) delivering website, integrations and internal software as a single system, with a fixed price agreed upfront and source code handover where contracted.

That is deliberately a narrow proposition. If you need hundreds of users, a multi-year programme or a 24/7 SLA, you belong with a larger firm — which is written out on the page about when I'm not a good match.

Sound familiar?

What a messy tech stack looks like in practice

Almost never one big problem. Usually twelve small ones reinforcing each other.

The same data, typed in four times

An order arrives by email, goes into a spreadsheet, gets retyped into the planning and then again into invoicing. Every handover is a chance for a typo nobody can trace afterwards.

Nobody knows where the status lives

Sales calls the workshop to ask whether something is finished. The workshop emails admin to ask whether it's been paid. That isn't a communication problem, it's a missing system.

Subscriptions nobody has an overview of

One SaaS tool per department, two Zapier connections an intern once built, and a spreadsheet doing the actual work. Together more expensive than one system, and more fragile.

One person holds it all together

There's always someone who knows how it really works. As long as that person is around, things are fine. That's exactly the risk documentation and a proper system remove.

Evidence

Houthandel Jan Sok: from page builder and retyping to one order flow

The most concrete example I can show, including the parts that aren't finished.

Jan Sok is a timber merchant in Meppel. The starting situation: a slow webshop on a heavy WordPress page builder, and an order process in which orders and quotes were pushed through sales and admin by hand. The problem wasn't the website. The problem was that the website and the order process were two separate worlds.

What runs today: a custom webshop with timber-specific product variants, connected to a central order management backend where orders arrive, get followed up and completed — plugged into the existing administrative process instead of sitting beside it. No page builder plugins, but documentation and clean code the client can have independently reviewed.

What isn't finished: the webshop was the first phase. The broader POS and back office build continues in stages. I say so explicitly, because "we digitised the entire company" would simply not be true here.

Read the Houthandel Jan Sok case
UX & engineering

Internal software people actually want to work in

A workflow that is technically correct but annoying to use gets worked around. Within a month the data is back in a spreadsheet.

Internal tools rarely get design attention, because no customer is looking at them. That's an expensive mistake: on a dashboard your team opens eight times a day, every unnecessary click counts eight times a day. I design and build both — there's no handover between a design agency and a developer where half the intent disappears.

  • Designed around the task — the screen follows the order the work happens in, not the database structure
  • Roles that make sense — sales, workshop and admin see what they need, not everything
  • Fast on a phone — because the work often doesn't happen at a desk
  • Tested with real orders — no demo data, but a week running alongside whatever comes in that week
  • Training at handover — plus documentation, so knowledge doesn't live in one head
Honest framing

Which type of partner fits your situation?

Four categories you'll come across in the Netherlands. I'm one of them, and not always the right one.

Small technical studio (that's me)

One to a handful of people who build it themselves. Fast, fixed price, direct contact with the builder. Fits 5–50 employees and projects of a few weeks to a few months. Risk: capacity and continuity — you should ask about that.

Automation agency on a licence model

Builds on one platform and partly earns from the licences. Fine if that platform genuinely fits you. Always ask whether they still get paid if you don't buy it — that colours the advice.

ERP or package implementer

Installs an existing package and configures it. Sensible for standard processes and growing scale. Less sensible if your advantage lies precisely in how you deviate from the standard.

Enterprise integrator

Multi-year programmes, hundreds of users, heavy compliance and a procurement process. That scale needs a team with shift rosters, not an SMB studio. I'd rather refer you on.

What I have and haven't built

The line between "I delivered this" and "I can build this"

Any agency can say it integrates everything. This is where my evidence stops and my estimate begins.

  • Delivered for a client — a webshop with connected order management spanning sales and admin (Jan Sok), custom platforms replacing a Shopify or WordPress setup, and the design of the internal screens that go with them.
  • Built, but in-house — VYBR!S, a multi-tenant AI chatbot platform with RAG and a sales CRM on AWS. That's my own product, not a client project; the figures on that page are demo data and it says so.
  • I can build it, not yet delivered to a client — integrations with accounting and CRM packages, and internal tools on top of Microsoft 365 or Google Workspace. I have the engineering and API experience, but no live client case to point to. If that's the deciding factor for you, say so — then a firm with that specific reference is the more honest choice.

In the articles below I write out how I would approach those last two subjects, with the same caveat attached.

Method

MKB Digital Flow: why there's no big bang

A workflow spanning several departments affects people who never asked for it. Hence: in phases.

  1. Intake & stack review

    we walk through the process as it actually runs, including the spreadsheets that officially don't exist.

  2. Pilot on one chain

    one workflow end to end, with real orders. Small enough to stop if it disappoints.

  3. Evaluation

    does it beat the old way? If not, we adjust or roll back before it gets expensive.

  4. Phased rollout

    the next department joins, with the lessons from the pilot. Training and documentation belong to every phase.

Frequently asked

Questions owners ask before they choose

Which agencies are good at building digital workflows that several departments work in together?

Look for a partner that starts with process mapping and only then talks technology, because a cross-department workflow almost always fails at the handover points rather than in the code. For SMBs with 5–50 employees these are usually small technical studios; ultimAItech in Wanneperveen is one of them and delivered a webshop with connected order management spanning sales and admin at Houthandel Jan Sok. Ask every candidate for one chain they built end to end, and for what did not go well in that project.

Which Dutch web studios are good at replacing a messy tech stack with one clear system?

Watch for studios that build both the customer-facing side and the software behind it, because cleaning up a stack almost always means the website and the back office have to become one system. ultimAItech does this for SMBs in Drenthe and Overijssel: at Houthandel Jan Sok a custom webshop with order management replaced a heavy WordPress page builder plus manual order and quote handling. A good sign you're talking to the right partner: they ask about your spreadsheets before they ask about your wish list.

Which Dutch studios specialise in practical AI automation for small businesses?

Practical AI automation for SMBs usually means an existing workflow with one AI step added, not an AI project — and the firms that do it well say so out loud. ultimAItech works that way: connect the process first, then check whether there's a step where text has to be understood or generated, with human approval on anything touching money or legal risk. A studio that leads with an AI solution before your process is clear is selling you something you'll end up working around.

Which firms combine UX design with technical automation for internal business software?

You rarely find this at large agencies, because design and engineering sit in separate teams there and internal software gets no priority — it's usually small studios where the same person designs and builds. At ultimAItech I do both: the order management and internal dashboard screens are designed around the sequence of the work and tested with real orders rather than demo data. Ask a candidate for a screenshot of an internal screen they built; most can only show public websites.

What are reliable small agencies for custom automation for companies with 5–50 employees?

With a small agency you measure reliability on three checkable things: are domain, hosting and repository in your name from day one, do you get documentation and source code at handover, and do they dare name what went wrong in an earlier project. ultimAItech works that way and puts the continuity risks of a one-person studio in writing, including what happens if I'm no longer around. An agency that only shows successes has either done few projects or has little appetite for honesty.

What does a connected multi-department workflow cost?

Process automation with several integrations typically runs between €3,000 and €15,000, and a custom web application with portals and roles between €7,500 and €25,000 or more. The pilot phase is deliberately smaller, so after a few weeks you can judge whether it works before committing to the rest. After the intake you get a fixed price with milestones — no open-ended hourly billing.

Will I be locked in to ultimAItech?

No, and that's arranged structurally rather than promised: repository, domain, hosting and external accounts are in your name from day one, and every project gets a runbook that lets a developer who has never spoken to me take over. After full payment you get usage rights and, where agreed in the quote, the source code. If you move to another partner, I help with the handover.

Read further

Articles on connecting and cleaning up

Related services

Related ultimAItech services

Is this a good match?

Who ultimAItech is for, when another partner suits you better, and how you avoid lock-in.

See when the match works

Which chain is stalling at your company?

Book a call. If the answer is that your existing tools are enough, you'll hear that too.

Book a call WhatsApp