Invoices, werkbonnen, materials, schedules: the coordination that lives in Word files, chat threads and one person's memory. We build the system that holds it, with an assistant that prepares the admin.
A Dutch contractor runs invoices, materials and his assistant from his phone. A university department plans its whole teaching year in one system.
The call is free. We look at one process and tell you honestly whether it is worth building. If it isn't, we say so.
Both started as one conversation about one process. Both are run by the people who asked for them, every working day.
Civil-engineering subcontractor, Netherlands · in daily use since September 2026
University department, Kosovo · in production since 2025
Screens show demo data. Real records stay private.
Most firms buy an app, a back office and an AI tool from three vendors, then glue them together with people. We build the three as one: every screen and every answer comes from the same records.
On the phone at the site or in the browser at the desk, built around your own unit of work: the werkbon, the order, the batch, the case.
Bajgora: a new invoice that carries the client's project and werkbon number.
Records, documents and numbers in one place: the PDF for the client, the export for the accountant, a live view of what is open, late or waiting on someone.
Student Hub: who teaches what, for which group, with every hour accounted for.
Ask it in plain words and it answers from your own records. It drafts, reminds and files the small requests, and it asks before it changes anything.
Bajgora: the assistant in Telegram asks “klopt?” before it writes.
Every automation we build has the same shape: something arrives, the system reads and checks it, a person confirms, and the result lands where it is needed. Here is the next one we are building into the Bajgora system.
The client's werkbon comes in as a PDF in the mail or a photo from the site.
Nobody retypes it.
Project number, bon number, hours and materials are taken off the page.
Nothing to do yet.
Matched to the project, priced from the supplier lists, the VAT rule applied. Anything unclear goes on a short list.
Only the unclear cases need a look.
The draft invoice waits on the phone, every line traceable to the bon.
One look, one tap: klopt.
PDF to the client, a copy for the accountant, the overview updated.
The money side is current the same day.
One conversation, following a single job from the first message to the paid invoice. Where the hours go becomes visible.
Projects, bons, materials, people, deadlines: the records everything else reads from, named the way your company names them.
The app, the system and the assistant on those records. You follow every step on a live progress page and decide on review pages, not in mail threads.
Two weeks in your real work, adjusting what the work shows. Then it is yours, and Care keeps it running.
| Before | After |
|---|---|
| Typed twice, in two places | Typed once, where the work happens |
| Invoices at the end of the month | Invoices the day the work is signed |
| “Ask Marieke, she knows” | Everyone sees the same state |
| Calling the office for a number | Asking the assistant |
A starting list from the work we know. Each one follows the same shape: the system does the routine part, and a person makes the call.
| Automation | When | The system | A person |
|---|---|---|---|
| Werkbon to invoiceA signed werkbon comes in: the system drafts the invoice with project, bon, hours and materials, and a person confirms with one tap. | A signed werkbon comes in | drafts the invoice with project, bon, hours and materials | confirms with one tap |
| Daily site reportThe crew sends photos and a voice note: the system turns them into a dated report for the client, and a person adds a line and sends it. | The crew sends photos and a voice note | turns them into a dated report for the client | adds a line and sends it |
| Crews and hoursA crew arrives on site: the system books the hours to the project and fills the weekly overview, and a person approves the week for payroll. | A crew arrives on site | books the hours to the project and fills the weekly overview | approves the week for payroll |
| Automation | When | The system | A person |
|---|---|---|---|
| Orders into productionAn order arrives by e-mail or from the web shop: the system puts it in one queue and proposes the production batch, and a person plans the day. | An order arrives by e-mail or from the web shop | puts it in one queue and proposes the production batch | plans the day |
| Batch records and documentsA batch leaves the line: the system keeps recipe, lab result and batch number, and prepares the safety data sheet and certificate for each delivery, and a person signs off the batch. | A batch leaves the line | keeps recipe, lab result and batch number, and prepares the safety data sheet and certificate for each delivery | signs off the batch |
| Delivery to the installerMaterial is ready: the system links the delivery to the installer's project, so the crew knows what arrives when, and a person changes the date if the site is not ready. | Material is ready | links the delivery to the installer's project, so the crew knows what arrives when | changes the date if the site is not ready |
| Automation | When | The system | A person |
|---|---|---|---|
| Document intakeDocuments arrive through five channels: the system sorts, names and files them before anyone opens them, and a person handles only what it could not place. | Documents arrive through five channels | sorts, names and files them before anyone opens them | handles only what it could not place |
| Missing documentsA deadline approaches: the system reminds the client and shows who is late, and a person calls the two who never answer. | A deadline approaches | reminds the client and shows who is late | calls the two who never answer |
| Deadlines and handoversWork moves between people: the system keeps one calendar of what is due, for whom, by whom, and a person sees the week at a glance. | Work moves between people | keeps one calendar of what is due, for whom, by whom | sees the week at a glance |
Your process is not on the list? Most are not. Describe it, and we tell you honestly whether it is worth automating. Request a 30-minute call
Deutschland · auf Deutsch
Belege aus fünf Kanälen, manuell sortiert, bevor die eigentliche Arbeit beginnt. Wir bauen den Eingang vor DATEV.
Zur Seite für KanzleienNederland · in het Nederlands
Werkbonnen via WhatsApp, planning in Excel, facturen overgetypt. Wij bouwen de app voor de bouwplaats en het systeem erachter.
Naar de pagina voor bouw en productieKosovo and beyond · in English
Departments that coordinate people, schedules and documents across many small handoffs. Student Hub runs one of them.
See the Student Hub case study
WuWei Labs is led by Agon Bajgora, a software engineer with more than ten years of experience and Head of the Computer Science & Engineering department at the University of Mitrovica “Isa Boletini”, where Student Hub runs the department's daily teaching operations. He holds an MSc in Informatics Engineering and is completing a PhD in AI on multi-agent systems at Ss. Cyril and Methodius University.
The name comes from the Taoist idea of Wu Wei, effortless action. The best systems don't demand attention; they flow. That is the standard: software that quietly does its job, people deciding what matters, and an honest “no” when a build is not the answer.
WuWei Labs is small by design. The person on the call is the person building the system. German-speaking firms talk to Sami Bajgora. Research, qualification and reporting run on our own AI operating system, so you can see how we automate ourselves before you pay us to automate you.
Every engagement starts small and earns the next step: one conversation, a written plan with a fixed price, a first working version in one to two weeks, and progress you can follow every week on a live progress page. Prices are public because you should not need a sales call to learn them.
€1,500 · 5 business days
A paid diagnostic of one real workflow: where the hours go, what to build first, what it costs, and what to leave alone. Credited in full against a pilot booked within 30 days.
€6,000–12,000 · 2–4 weeks
One workflow live in production, measured on your real work. Half at kickoff, half at go-live, with go-live defined in writing at kickoff.
€15,000–35,000 · 6–10 weeks
The app, the office system and the assistant for a whole operation, with a native Android or iOS app where field work needs one. The Bajgora system is this step.
from €500 / month. After delivery: monitoring, fixes and steady iteration. Sold at the results review, never before delivery.
If the Teardown finds nothing worth building, you keep the report and we stop. If a pilot does not reach the go-live we agreed in writing, the second half is not due.
The ladder is public: the Workflow Teardown is €1,500 and is credited against a pilot. Pilots are €6,000–12,000. An operations system is €15,000–35,000. Care starts at €500 a month. You get a fixed quote in writing before anything starts.
If a package fits your process, buy the package; the Teardown will tell you. We build when your process is what makes you different: a factory and an installer in one group, a price list nobody else has, crews who work in three languages.
A first working version usually exists in one to two weeks, and a production pilot in two to four, depending on integrations. The Bajgora app was on the owner's phone two weeks after the first conversation.
Only where the current tool is Word, paper or a spreadsheet. Systems that work, like DATEV or your accounting package, stay; we connect to them.
No. The assistant answers, drafts, sorts and flags. Anything regulated, financial or judgment-shaped goes to a person, and it asks before it writes anything.
Under a processing agreement (Art. 28 GDPR), with EU hosting, and with §203-aware confidentiality for German professional firms. Deployment inside your own infrastructure is possible where that is the right call.
In Mitrovica, Kosovo, on Central European Time. Our systems in daily use are in the Netherlands and Kosovo. Builds are run in English; German-speaking firms work with Sami Bajgora, and Dutch-language questions are answered in Dutch.
Then the Teardown report says exactly that, and we stop there. That honesty is what you pay for, and it costs less than finding out after a build.
One process, one conversation. You get an honest view of whether it is worth building and what it would cost. If a call feels too soon, the Workflow Teardown (€1,500, five days, credited against a pilot) is the concrete first step.
No spam. No sequence. A reply from Agon within one business day.
Prefer LinkedIn? linkedin.com/in/agonbPrivacy notice
