Industry
Professional services - digital solutions.
Documentation, proposals and team knowledge.
When clients usually bring us in
- the existing system no longer keeps up
- the work happens in spreadsheets
- data is duplicated across systems
- you need a new application
- you want to modernise an old system
- you're building a new digital product
What this means for you
- a solution that respects how your sector actually works
- we start with the part that pays off first
- one team for the digital and the physical side
What we can digitalise
- proposal preparation
- document workflows
- RAG over the archive
- CRM and reporting
- back-office automation
In professional services the knowledge is scattered
In legal, consulting, accounting and engineering firms the most valuable asset is what people have already written: proposals, opinions, reports, contracts, calculations. That material usually sits in folders known only to whoever created them, so similar work gets done again from scratch.
- search across the archive, with citations and access rules
- proposal preparation from existing material
- document workflows with approvals
- records of cases, deadlines and owners
- connection to accounting and invoicing
- reporting on workload and case profitability
- automating the admin your specialists do today
Access rights come first here
In professional services the content is often confidential and tied to a specific client. Any search or AI system must therefore respect who may see which document - and must not reveal it indirectly either, through a summary or an answer.
If a user has no right to the source document, the system must not show its content merely because the document is in the index.
A typical case
The example illustrates the type of task, not a specific client.
A consultancy prepares proposals by having someone find a similar past proposal - if they remember it exists. The system makes the archive searchable by meaning rather than by file name, with citations and respecting access rights, and drafts a proposal from the material that this particular person is allowed to see.
How such a project runs
Process mapping
Mapping where material is created and where it gets lost.
Requirements and criteria
Who may see what, and what may be used to draft new material.
Design and prototype
Testing search against your team's real questions.
Phased build
Search first, then drafting and workflows.
Rollout and support
Go-live with the people who actually write the material.
What you receive
- a working system in production, with a separate test environment
- documentation of the process, the rules and the integrations
- user guides and training for your team
- test scenarios and acceptance test results
- access, source code and data under the agreed model
- an evaluation set with known answers to check quality
Signs that it is time for a change
- proposals are written again although a similar one exists
- the archive is large and searching by file name does not help
- document approvals happen over email
- case deadlines are tracked in a spreadsheet
- specialists spend time on admin instead of expert work
- knowledge leaves when a person leaves
How we work in this sector
Where we start
We look at which processes run manually, where data is duplicated and what would deliver the biggest effect.
First step
We start with a bounded scope that can be rolled out quickly and measured.
Scaling
Once the first part works, we add the next step of the process or the next location.
Support
After rollout we stay available with an agreed response time.
Related work
FAQ
Will the AI see documents an employee has no right to?
No. Permissions are enforced at retrieval, not at display - what a user may not see never enters the answer.
Do our documents go to an external provider?
Where processing happens is decided against your requirements, before development starts rather than after.
Related solutions
Sounds like your project?
Send us the project description, your existing system, the tender documents or the event date.