Questions, answered
Before you
replace a role
The useful questions are about the work, the boundaries and what happens after launch. Here is how we approach them.
Fit and role replacement
Do you replace whole roles?
Where assessment and testing show that the agreed work can be handled reliably, yes. We map the complete role, its volumes and its exceptions before proposing replacement. A repetitive task within a role does not automatically make the entire role eligible.
Who is SOZ for?
We work with service companies with structured operations and recurring workloads. Enquiries, intake, scheduling, CRM administration, routine documents and status reporting are useful starting points.
What will you not automate?
Finance, payroll, regulated decisions and autonomous personnel decisions are outside this offer. We also do not provide employee surveillance or automated productivity scoring.
Can I enquire about a workflow rather than a job title?
Yes. Describe the work and the tools involved. The assessment determines whether a bounded workflow or an eligible role can be replaced and how the scope should be defined.
Building and running it
How do you decide whether the replacement works?
The proposal defines acceptance criteria before implementation. We test representative requests, incomplete information, exceptions and failure cases with your team, then record the results before production acceptance.
Who makes decisions outside the agreed rules?
Your team does. We define escalation points and owners so the automation does not invent authority when a request falls outside its scope. Commercial promises, unusual cases and approvals remain with the people named in the agreement.
Will we need to replace our existing tools?
We build around existing tools where practical. The assessment checks what can be integrated, what access is available and whether a proposed connection is appropriate. Required changes are made clear in the proposal.
How long does implementation take?
The schedule depends on the work, the integrations and the testing required. We agree it in the proposal after assessment. We do not promise a standard delivery time before seeing the role.
Where will the solution run?
Deployment is agreed for each engagement. Client solutions are separate from this public website, with their own access, permissions and operational arrangements. The proposal identifies the relevant providers and responsibilities.
The fee and the first year
How is the fee calculated?
We assess the workload, integrations and operating requirements, then propose one fixed first-year fee. The proposal defines what is included, the usage allowance and how changes are handled. You approve the price before implementation begins.
What is included for 12 months?
Implementation, hosting, AI usage and maintenance within the proposal’s agreed workflows and usage allowance. The support commitment and acceptance criteria are also defined in writing.
When does the included year begin?
At production acceptance, after the agreed checks. Development time does not consume the 12-month operating period.
Is usage unlimited?
No. The quote is based on an assessed workload and a stated usage allowance. The proposal explains how increased volumes, new workflows or other material changes are handled.
Do you guarantee a particular saving?
No general savings guarantee is made by this website. A useful comparison depends on the cost of the existing work, the scope being replaced and the client’s actual operating decisions. Any engagement-specific commitment must be set out in its agreement.
What happens after the first year?
You can choose a separately quoted hosting and support renewal or a documented handover. There is no automatic renewal. Ownership, licences and the handover requirements are specified in your agreement.
Starting a conversation
What should I put in the enquiry form?
Describe the role, its routine tasks, approximate volume and the tools involved. A general account is enough to start; you do not need a technical specification.
Should I send employee or customer records?
No. Leave out employee records, performance information, customer data, credentials and confidential documents. Any later data-sharing or access arrangement is agreed separately.
Does submitting the form commit us to a project?
No. An enquiry starts a conversation. Scope, pricing, responsibilities and payment terms are agreed in a separate written proposal before an engagement begins.
Who receives the enquiry?
SOZ enquiries are delivered to enquiries@soz.to. We use your details to respond and discuss the possible engagement. The website does not maintain a separate database of enquiry submissions.
The next step
Ask about your own workflow
If the answer depends on how your business works, send us a short description of the role.