Skip to content
How we work

How we work: from first call to maintenance

We take one recurring process, build it on the systems already in place and run it alongside the existing work first. Then we maintain it and build the next one together.

The Winvent team in conversation at a table, laptops open
The process

Five steps to a system of your own.

  1. Conversation

    We talk about where the manual work sits, which departments it touches and which systems are in place. Where needed, IT and the process owner join.

  2. Task and fixed price

    We scope one task and agree the price up front, and who gets access to which data. You approve that before we build.

  3. Building on your systems

    We build the steps as code on the systems already in place, where possible in your own environment and accounts.

  4. Live

    The first version runs on real data, tested in a separate environment and alongside the existing process first. You decide whether it goes live.

  5. Management and maintenance

    We maintain the code and adjust the system when the work changes. We fix bugs in our code at no additional charge. Management and maintenance are billed separately; we agree that amount up front.

How it grows

The next process

Once the first process works, we choose the next one together. The same route, on what is in place by then.

What we offer

What we build

  1. AI Automation and Agents

    Software that takes over recurring tasks on the systems you already use.

    • Runs on the systems already in place
    • Every step can be read back
    • Unclear cases go to a colleague, with the reason
    • We maintain the code, with no per-user licences

    Example

    A work order arrives as a PDF. The system reads it, links it to the schedule and prepares the hours for invoicing. If something does not add up, the work order goes to a colleague with the reason attached.

  2. AI Products

    A complete AI product for your clients or colleagues, from first sketch to live.

    • Runs in your own environment
    • Built on your own data
    • A colleague approves every answer before the client sees it
    • We maintain the code

    Example

    A client submits a request through a portal. The product reads the request, adds what it needs from your systems and prepares a draft reply. A colleague approves it, then it goes to the client.

  3. Custom Platforms

    A platform or dashboard built around the way you work, wired into what is already there.

    • Connected to the systems already in place
    • Built around the way you work
    • The planner keeps the final say
    • We maintain it and help it grow

    Example

    Every morning the planning board pulls the jobs from two systems and puts them side by side, with what is still missing. The planner sees on one screen what needs arranging and moves what needs moving. The board decides nothing.

  4. Company Brain

    A knowledge system in which your team searches the company's own information.

    • Searches only your own information
    • In a separate database of its own
    • Every answer comes with its source
    • We maintain the connections

    Example

    A colleague asks a question. The system searches the documents and conversations the company connects and answers with a reference to the piece it comes from. The colleague checks the source and decides what to do with it.

Choosing the first repetitive task to automate is a question in itself. We wrote down how to recognise a good first task.

Control

Fits your organisation. Stays under your control.

The work rarely sits inside one department, and IT, security and procurement want to know up front how a system handles your data. We agree this before we build.

Which systems we connect
How it fits
  • Across departments

    An order touches sales, planning and administration. We build one of those handovers, with the process owner and IT at the table.

  • On what is already there

    The steps become code on your existing systems. No extra package, and no per user licence.

  • Alongside the existing process first

    The first version runs on real data and next to the current work, until you decide it goes live.

How it stays under control
  • Your environment and accounts

    Where possible the system runs in your own environment and accounts. Data and accounts stay yours, and you get documentation.

  • Access to that one workflow

    The system can only reach what the agreed workflow needs.

  • Every run can be read back

    What came in, which steps the system took and what went out.

  • A person signs

    Anything that goes out or moves money is approved by someone. When unsure, the system says so instead of guessing.

  • NDA and processing agreement

    Both standard.

  • No training on your data

    We do not train public models on your data.

From two client cases

Time two clients got back

Results from our two published cases, for those two processes.

Screening documents

Forta Solutions

Result in the case

8 hours a week back

Keeping the pipeline current

Match Masters

Result in the case

2 hours a day saved

Case results, not a measurement that holds for every process.

Read how we built it
Questions

What you may still want to know

Which systems does it connect to?

To the systems you already use. For each system we look at which connection exists and build on that. The Integrations page shows how that works with SAP, Odoo, Salesforce and Microsoft 365, among others.

When is the first version ready?

Within two weeks there is a working first version for one agreed task, on your real data and tested in a separate environment. Then you decide whether it goes live.

What does it cost, and what does it cost afterwards?

We agree the build price up front, for one task. You approve it before we build and you pay after delivery. We fix bugs in our code at no additional charge, and our software carries no per-user licence. Management and maintenance are billed separately; we agree that amount up front. Running costs such as hosting, model usage and third-party services are also named up front.

What does the system do when it is not sure?

It says so instead of guessing, and the case goes to a person with the reason attached. Anything that goes out or moves money is approved by someone.

What if something breaks?

We keep monitoring and maintaining the system and reply within one business day. There is a fallback built in, so an outage does not stop the work.

Which sectors do you build for?

Mostly building services and construction, logistics and cleaning, plus the office work that comes back every day. Recruitment runs through our agency Plaatsr, hotels through hosp., warehouses and 3PL through Pakr.

Get started

What would you automate?

The first conversation is free. We reply within one business day.