Services
What each service includes and how long it takes
Every service starts from the problem it solves. Timelines are estimates based on work of comparable scope: when a case carries more uncertainty, the range widens instead of promising short.
Assessment and roadmap
Two weeks to learn what is worth fixing first in your company, and what is not.
- Estimated timeline
- 2 to 3 weeks
The problem
You know some processes eat hours every day, but not which ones are worth automating or what it would cost. Without those two numbers any decision is a bet, and a lost bet here is measured in months of work and budget spent.
What you get
- A survey of the processes that consume the most time, with measured volume and hours.
- An hours-and-savings estimate for each case, ranked by which is worth solving first.
- A list of what is not worth automating yet, with the reason for each one.
- A technical decision record, so any provider can execute the plan.
Assistants that answer from your documentation
You stop answering the same ten questions by hand every day.
- Estimated timeline
- 4 to 8 weeks
The problem
The same questions come up every day: pricing, lead times, order status, how something works. They get answered by hand, late, and the answer changes depending on who replies that day.
What you get
- An assistant that answers from your actual documents, not from general internet knowledge.
- Every answer cites which document it came from, so it can be verified.
- Defined boundaries: what it answers on its own and what it hands to a person.
- A panel of the questions it could not answer, showing what is missing from your documents.
Process automation
The programs you already use pass data to each other, with no copy and paste.
- Estimated timeline
- 3 to 6 weeks
The problem
Data moves between systems by hand: from email to spreadsheet, from spreadsheet to your management system. Every hop is lost time and a chance for an error that surfaces weeks later, once it has already been invoiced.
What you get
- Processes that run on their own, with a log of every run you can check.
- Alerts when something fails, so you hear it before the customer does.
- Documentation of how it was built, so it does not depend on whoever built it.
Internal knowledge search
Find in seconds the fact only one person knows today.
- Estimated timeline
- 4 to 8 weeks
The problem
The information exists: it is in contracts, manuals, minutes and shared folders. The problem is finding it. People end up always asking the same person, who becomes a bottleneck for the whole team.
What you get
- Meaning-based search that finds the document even when you do not use the exact words.
- Per-area permissions: each person finds only what they are allowed to see.
- It updates on its own when a document is added or changed.
Custom product with AI
The system you need, with no per-person licences and everything in your name.
- Estimated timeline
- 8 to 16 weeks
The problem
What you need does not exist off the shelf, or it does but charges per seat and does not fit how you work. You need something of your own that will not be abandoned in six months when whoever built it disappears.
What you get
- A web or mobile application actually running, with the whole build in your name.
- Automated tests that run on every change, from day one.
- Documentation of how it is built, so another team can pick it up.
AI evaluation and security
Know whether your AI answers well, and that it does not say what it shouldn't.
- Estimated timeline
- 3 to 5 weeks
The problem
You already have something with AI running, but nobody knows whether it answers well. «Seems fine» is not a measurement, and the day it tells a customer something wrong or repeats private data, you will hear it from the customer.
What you get
- A set of questions with their expected answers, run on every change.
- A check that blocks releasing a version if quality drops below the agreed minimum.
- Input and output filters against data leaks and misuse.
- A review against the risks already documented for this kind of application.