Built for your business. Cared for over time.
A managed annual engagement brings the initial implementation and ongoing technical care into one relationship, with scope and terms agreed before work begins.
One relationship.
A clear commitment.
We aim to make tailored software and AI accessible without a large upfront development bill. Your proposal sets out activation, the annual service, any usage charges, and the payment schedule.
Pricing follows the workflows, systems, delivery complexity, and ongoing support your business needs.
Discuss an engagementYour agreed scope can include
- Process discovery and workflow redesign
- Custom applications and operational dashboards
- AI agents and workflow automation
- System integrations and organized knowledge
- Team training and rollout support
- Monitoring, maintenance, and repairs
- Regular reviews and a prioritized improvement plan
A proposal you can understand operationally and commercially.
An annual service needs more clarity than a feature list and a monthly number. Your agreement should make the first delivery, recurring service, dependencies, and limits understandable.
Initial scope and acceptance.
The proposal identifies the workflow, users, applications, connections, and agent capabilities included in the first release. It sets out milestones, acceptance criteria, assumptions, and customer responsibilities. Discovery scope and any separate assessment fee are agreed explicitly.
Activation, recurring fees, and usage.
The commercial schedule explains any activation fee, annual commitment, payment schedule, included allowances, and separately charged usage. It identifies relevant third-party services and who pays for them. Exact pricing follows the assessed scope; there is no universal published package price.
Support, review, and operating boundaries.
We document the supported system, issue-reporting route, response arrangements, review cadence, and maintenance responsibilities. Required availability, recovery, or information-handling commitments must be assessed for the specific engagement rather than inferred from a general service description.
We care for the technology. Your team owns the business decisions.
A managed model reduces the need to assemble and supervise a technical stack internally. It still needs an engaged business owner and people who can confirm how the work should run.
Thology's agreed delivery responsibilities.
The scope can cover process analysis, implementation, integrations, evaluation, deployment, staff guidance, monitoring, maintenance, and repairs. We make technical dependencies visible and explain decisions that affect reliability, cost, or the operating workflow.
Your team's contribution.
A sponsor sets priorities, a process owner confirms rules, and representative users provide feedback. The business arranges approved access, owns its operating policies, and assigns reviewers for consequential or ambiguous cases. Any vendor or data-preparation dependencies are identified in the plan.
A shared view of progress.
Reviews connect work completed with actual usage, quality, exceptions, operating costs, and the measures in the business case. The discussion should lead to a clear action: fix a problem, refine the process, test an assumption, or consider a separately scoped improvement.
Maintain what is agreed. Expand with a clear decision.
A recurring engagement should make care dependable without turning into an undefined development commitment. The distinction between maintenance and expansion is documented in your contract.
See how the delivery stages workCare for the existing capability.
Maintenance addresses the supported application's operation and agreed dependencies. A failed connection, defective behavior, or recurring quality issue is assessed against that scope. The contract defines coverage and any exclusions, so support expectations are concrete.
Assess new work before committing it.
A new department, workflow, agent role, or system connection may need additional design, testing, and ongoing support. We review the business value and dependencies, then agree whether it fits the existing scope or needs a separate commercial proposal.
Plan data access, renewal, and exit.
Your business data remains yours; the proposed model retains software and reusable IP with Thology. The agreement defines access, exports, retention, renewal, and what happens when the service ends. Those terms are settled before commitment rather than left to an assumption at the end of the year.
Clarity from the start.
A defined first release.
We agree the initial workflows, deliverables, responsibilities, and milestones after understanding the operation.
Transparent operating costs.
The proposal explains platform and service fees, usage allowances, third-party dependencies, and any separately billed costs.
Expansion by agreement.
New applications, agents, and integrations are prioritized together. Additional work stays within agreed scope or receives a separate quote.
Ownership in plain language.
The proposed model retains software and reusable IP with Thology. Your business data remains yours. Access, export, and exit arrangements belong in the contract.
Before you commit.
How much does it cost?
Pricing depends on the workflows, systems, complexity, and support required. We establish a defined scope and commercial proposal before you commit. We do not publish a universal price because the work and operating requirements differ between businesses.
What is included after launch?
Monitoring, maintenance, and repairs for the agreed system are included in the annual contract. Reviews identify further opportunities. Additional capabilities are either delivered within the agreed scope or separately quoted.
Who owns the software and the data?
The proposed service model retains software and reusable intellectual property with Thology. Your business data remains yours. The contract defines access, permitted use, export arrangements, third-party dependencies, and what happens at the end of an engagement.
How quickly can we see working software?
We aim to put a useful first release in front of your team early. The actual schedule depends on scope, data readiness, access to existing systems, and team availability. Milestones are agreed after discovery rather than promised before the work is understood.
Start with the work that slows you down.
Tell us where your team loses time. We’ll help you identify a practical first improvement.