01
Client
Intake
Client facts and supporting documents are collected once.
Industry · Professional services
Software that protects expert time and makes client work easier to follow.
Thalenor builds intake systems, client portals, matter or engagement workflows, document automation, knowledge retrieval and reporting for firms whose work depends on expertise, evidence and review.
SOURCE · JUDGEMENT · DELIVERABLE04
A clear answer
What does Thalenor build for professional services organisations?
Professional-services software should reduce coordination around the expert work without flattening the judgement inside it. Thalenor designs systems that structure intake, documents, tasks, approvals, client communication and reporting while keeping professional review explicit. AI can help find, compare, classify and draft from authorised sources; it should not invent authority or issue consequential advice without the responsible professional.
Workflow in view
A credible product should make the work visible before it tries to make it fast.
Follow the record, the responsible role and the decision that must remain human.
ILLUSTRATIVE MODEL · FICTIONAL RECORDS
A client document moves from structured intake to professional sign-off with its authority intact.
The system accelerates assembly and review without presenting a generated draft as finished professional work.
EVIDENCE → JUDGEMENT → DELIVERABLE
ILLUSTRATIVE OPERATING MODEL · 06 STATES02
Intake
Validate
Missing or conflicting information enters a review queue.
03
Assistance
Assemble
The approved template and clauses produce a marked draft.
04
Professional
Professional review
Judgement points are resolved and unsupported text is removed.
05
Client
Client decision
The client reviews only the appropriate questions and version.
06
Professional
Finalise
The approved output, authorship and source record are preserved.
Illustrative workflow. Professional, legal, regulatory and retention obligations depend on the firm and jurisdiction.
Boundaries built into the product
Responsible software states what it will not decide.
A disclaimer cannot compensate for a workflow that hides uncertainty or lets sensitive actions happen without ownership.
01
Professional judgement
Automation prepares and organises; the responsible professional owns advice, approval and final output.
02
Privilege and confidentiality
Access, logging, external processors and retrieval boundaries must follow the firm’s obligations and policy.
03
Source authority
Generated answers and documents should identify the precedents, policies or client facts they rely on.
04
Version control
Draft, reviewed, approved and executed artefacts must remain distinguishable.
05
Client visibility
Portal transparency should not expose internal notes, other clients or privileged deliberation.
Operating landscape
One connected operation. Six places where context can break.
The system should carry meaning across these hand-offs, not leave users to rebuild it in messages and spreadsheets.
01
Client intake
Service fit, identity, conflict or eligibility checks, scope inputs, documents and an accountable next step.
02
Client portals
Secure requests, uploads, messages, milestones, approvals and deliverables in a relationship-specific space.
03
Matter or engagement workflows
Owners, tasks, dependencies, dates, review states and an honest view of what is waiting.
04
Document generation
Controlled templates, approved clauses, structured data, versioning, review and finalisation.
05
Knowledge retrieval
Permission-aware search over approved precedents, policies and work product with source citations.
06
Reporting
Workload, turnaround, exceptions, utilisation or commercial insight based on clearly defined operational states.
Where design judgement matters
The hard part is rarely the screen someone asks for first.
01
The first form should improve the first professional conversation.
Intake should collect what changes routing, preparation or eligibility—not reproduce an internal checklist in front of the client. Sensitive questions need purpose, explanation and proportionate access.
- AAdapt questions to service and prior answers
- BSave progress for document-heavy intake
- CRoute exceptions to a named reviewer
- DCarry structured context into the engagement record
02
Document automation starts with authority, not mail merge.
A dependable generation system knows which template and clause set applies, where each fact came from, which sections require judgement and who approves the final document.
- AVersion templates and clause libraries
- BValidate structured facts before generation
- CMark unresolved choices visibly
- DPreserve review and approval history
03
Retrieval should answer with evidence, permissions and useful abstention.
A knowledge assistant is valuable when it shortens the path to a source. It becomes risky when confident prose obscures missing authority, outdated material or access boundaries.
- AIndex approved, current sources
- BApply document-level permissions before retrieval
- CCite the passages used
- DAbstain when support is weak or conflicting
04
Clients need progress they can understand, not your internal task list.
A portal should translate internal work into meaningful requests, milestones and decisions while protecting internal notes and professional deliberation.
- ASeparate internal and client-visible states
- BMake requests specific and time-bound
- CShow what changed after an approval
- DKeep email as notification, not the only record
Relevant capabilities
The engineering disciplines this work usually touches.
Decision guide
Where document automation helps—and where it creates new professional risk.
Document-heavy work contains both repetition and judgement. The design challenge is to separate them without losing the evidence that connects the two.
Begin with a frequent, bounded document whose facts and approval path are already understood; do not begin with the most complex professional judgement.
01
Structure facts once
Client, matter and transaction facts should be validated in a shared record rather than retyped into each document.
02
Version the authority
Templates, clauses and policy sources need owners, effective dates and a route for withdrawal.
03
Expose unresolved choices
A draft should highlight missing facts and judgement points rather than smoothing them into plausible language.
04
Keep review attributable
Record who reviewed which version and what changed before approval or release.
05
Protect retrieval boundaries
Search and AI retrieval must apply access rules before content reaches the model or user.
06
Measure avoided rework
Useful outcomes include fewer missing fields, faster review and reduced version confusion—not simply documents generated.
Practical questions about professional services software.
Yes. We define identity, client and matter boundaries, document visibility, requests, approvals, notifications and the administrative support path before implementation.
Protect the judgement. Remove the avoidable handling around it.
Bring one client journey, document family or review bottleneck. We will separate the repeatable work from the decisions that must remain professional.