Construction
Project administration, subcontractors, tracking extra work.

Your business has more in it.
Give it room to grow.
We build AI systems that take care of everyday work. Connected to your software. Under your control.
↳ ONE ROUTE
You don’t have to choose between a control layer or a new system. It’s one route, and you start wherever fits your business.
We map one process — e.g. work order → invoice, or enquiry → quote. You get a concrete proposal, no obligation.
That one process runs automated, with policies and your approval at the important moments. Works on top of your existing AFAS, Exact or Salesforce.
Want to streamline more than one process, or have no CRM/ERP yet? Then grow into Smart 2: a complete business system with the automation already built in.
Already have an ERP or CRM (AFAS, Exact, Salesforce)? Start with the control layer on top of your current system. How it works
No system yet, or want to replace it? Start with Smart 2. Discover Smart 2
↳ FOR WHO
Pick your industry and see the pain points we solve directly.
Project administration, subcontractors, tracking extra work.
Work orders, material tracking, planning.
Fault service, service contracts, planning.
Reports, quote approvals, multiple stakeholders.
A NEW LAYER. YOUR EXISTING SYSTEMS.
Integration feasibility is assessed per implementation. Brand names are system references, not customer logos or partnership claims.
01 LESS WORK. MORE CONTROL.
From an incoming invoice to your approval. One place for processes, agents and decisions. Try it yourself.
See what’s moving, what’s waiting and where you’re needed.
You set the boundariesAbove the example limit of €5,000. Execution waits for an authorised reviewer.
INTERACTIVE PRODUCT DEMO Sample data. No real actions.
02 THE SPACE BETWEEN SYSTEMS
The invoice is in your inbox. The order is in your ERP. The approval is somewhere in an email. Your people are the connection.
SEMQO turns those disconnected steps into one controlled process. With an owner, explicit rules and visibility into what actually happens.
03 THE PLATFORM
SEMQO connects the people, agents and systems that run your operations.
Read the right data from your existing systems.
Select a step. External actions follow policy checks and any required approval.
05 THE CHAIN
Every layer does one thing. Visible, in order, with a person where that belongs.
Orders, stock and entries
Customers, deals and history
Incoming messages and attachments
Invoices and payment instructions
One layer for the work. One place for control.
Every proposed action against the configured limits
Above the limit, execution waits for a person
The action goes back into the systems
What happened, and on whose approval
Schematic view of the layers. No customer data.
04 GOVERNANCE BY DESIGN
An agent may be capable of an action. That does not mean it is authorised to execute it.
Define allowed actions per organisation. Let a policy determine whether execution may proceed, requires approval or must stop.
Amount and time rules are configured and tested per workflow. The policy below is an interactive design example.
€18,400 exceeds the example limit. Execution waits for review.
04 OPERATIONAL USE CASES
One process that works is worth more than ten disconnected experiments.
Extract data, match records and surface exceptions. Financial actions get the agreed controls.
Structure information, enrich CRM records and prepare a follow-up for review.
Validate orders, check inventory and prepare tasks. Exceptions stay visible.
Bring reports together, flag risks and route decisions to the right owner.
Implementation scenarios. Exact execution depends on your integrations, policies and acceptance tests.
05 BUSINESS SCANNER
Make your first estimate. No account. No automatic sharing of your business figures.
Automation Opportunity
45/100Priority index · not a benchmarkStart by exploring invoice processing and matching.
Model: FTE × monthly hours × 12 × hourly value. This is potential capacity, not guaranteed savings. Implementation and platform costs are not deducted.
Validate this in an assessment06 INTEGRATIONS
We start with what you already use. For each integration, we assess the API, permissions, data quality and the actions you need.
Providers available; configuration and testing per environment.
API integration subject to technical assessment.
Mail and calendars, depending on access and configuration.
Purpose-built connections with an explicit execution contract.
No official partnership status is claimed.
◇ SECURITY
Identity, policies, traceable decisions and recovery — part of every implementation.
See security◇ OBSERVABILITY
Follow actions, approvals and exceptions — with a live execution trace as an example.
See observability09 FROM MODEL TO EVIDENCE
Example implementation: invoice processing for a finance team. Not a customer case or promised result, but a concrete path to an evidence-based business case.
Volume, handling time, corrections and people involved.
Integration, owner, exceptions and approval path.
Net time saved after review work, platform costs and implementation.
10 INVESTMENT
Choose a scope that fits your operations. Configuration and service are confirmed in a proposal.
For a clearly defined process.
For connected processes.
FOR SCALINGFor more complex environments.
Discovery: €1,500–€5,000 · Implementation: €5,000–€25,000+. Existing indicative prices; final scope, tax treatment, external licences and SLA in the proposal.
11 GOOD QUESTIONS
You do not need to give up control to delegate work.
The control layer does not: it works on top of your existing system, which remains the source for your business records. If you want to replace your ERP, Smart 2 is the option for that.
This depends on the agreed implementation. Hosting, external model services, access and retention are agreed before the first workflow goes live.
An action requires an explicitly configured and tested integration. Financial actions are designed with appropriate authorisation and approval. The demo on this page makes no payments.
Capabilities can be disabled and workflows paused. An external action already executed cannot always be reversed, so stop and recovery procedures are agreed in advance.
A policy determines whether a capability may execute, requires approval or is denied. An authorised user decides; the workflow retrieves that decision. Approval alone does not mean the action is complete.
We assess available APIs, data sources and exports. Access, data quality and the desired action determine whether a reliable integration is possible.
We design validation rules and a path to human review for each workflow. Uncertain or invalid results should not silently lead to an external action.
Scope and timeline are defined after the assessment. Integrations, access, data quality and acceptance testing determine the delivery time.
Yes. Start with a defined process, a clear owner and a measurable baseline. Expand after execution and governance have been verified.
12 THE NEXT STEP
Discuss one process. We bring systems, manual steps and required controls together in a concrete proposal.
Calculate my potential first