Lay the groundwork for AI.
Make recurring work easier to run, without giving up control.
Groundlens helps you decide where AI belongs in recurring work, what should stay human, and where a simpler process is enough. If a focused setup makes sense, we test it in an environment you control and hand it over to the person who will run it.
Illustrative examples
Start with the work people repeat, not with an AI tool.
Useful AI work starts with a workflow that people can describe, review, and own.
The examples here show the kind of recurring friction we can examine. They are illustrations, not completed client projects or promised results.
Prepare an inquiry for review
Bring the relevant details together, flag what is missing, and leave the final decision with a person.
Check an incoming request
Spot missing information before someone replies. A person still decides what is correct and what happens next.
Reduce repeated copying
Move approved information between tools you already use, with a visible check before anything continues.
Use a simpler process when it is enough
AI is not the default answer. Sometimes the useful change is a clearer form, a better handoff, or leaving the workflow alone.
How control stays visible
A person still checks the work.
We make the approval point, the data boundary, and the end of the test explicit. The Pilot stays in one named test environment under your control and cannot write to production.
Moving beyond that test is a separate decision. It needs a new scope, the right access, and another approval. The person who runs the workflow remains visible throughout.
The workflow is unclear.
Use the Blueprint to map the work, the boundary, and the decision before anyone builds.
The workflow is clear enough to test.
Use the Pilot to test one focused setup and hand it to the person who will run it.
The problem spans more than one workflow.
Define a Foundation scope in writing before any larger engagement begins.
Offers
Choose the first step that fits now.
The Blueprint and Pilot are separate purchases. Either may be the first step. A broader Foundation scope is quoted separately.
AI OS Blueprint
One live day for a clear decision about a recurring workflow.
1 day
- Workflow and intended change
- Existing tools and data
- Ownership and approval
- Clear boundaries for the next step
- Written recommendation: proceed, defer, or stop
Pilot
A focused test setup in an environment you control, handed to the person who will run it.
3–4 days
- One clearly named recurring workflow
- One named test environment you control
- No production write access
- Documentation and handover to the operator
- Verification against the agreed scope
AI OS Foundation
A larger scope for several connected workflows, defined and quoted separately.
After a quote
- For an operating need that cannot be reduced to one workflow
- Scope, price, and timing are written before work starts
Fit check
Tell us where the work gets stuck. We review whether Groundlens is useful and which next step, if any, makes sense. The check is free.
Plan
The AI OS Blueprint is for work that still needs a clear decision. One day, about four live hours, €495 net. You leave with the workflow, boundaries, owner, and next decision in writing.
Focused setup
The Pilot is for a workflow that is already clear enough to test. €2,000 net, three to four days once prerequisites are met, in one named test environment you control. We hand it to the person who will run it.
Larger scope
The AI OS Foundation is for a broader operating problem that cannot be reduced to one workflow. Scope, price, and timing are agreed in a separate written quote.
Questions
Questions
What is Groundlens?
Groundlens helps you decide where AI belongs in recurring work, what should stay human, and where a simpler process is enough. If a focused setup makes sense, we test it in an environment you control and hand it over to the person who will run it.
What does the plan include?
The AI OS Blueprint is a one-day working session for €495 net plus applicable VAT, paid before kickoff. In about four live hours, you and up to five people map one recurring workflow and leave with a written proceed, defer, or stop decision. The session uses synthetic or anonymised material and does not touch production systems.
What does the setup include?
The Pilot is a focused setup for €2,000 net plus applicable VAT, split 50 percent on signature and 50 percent at handover. Over three to four days, once prerequisites are met, we test one workflow in a named environment you control and hand it to the person who will run it. It has no production write access and does not include or require a Blueprint.
Who is it not for?
Groundlens is for people who own a recurring workflow and can decide what happens next. Agencies, IT companies, and software companies are outside the buyer scope. Country and headcount are not eligibility gates.
Is there a client result yet?
Not yet. The proof section shows systems we have built and run ourselves, clearly labelled as internal builds. We will publish a client result only with evidence and permission.
Does the same work keep taking extra effort?
Tell us what happens. We will review the fit at no cost and work out the next useful step, including when no project makes sense.