Good questions.
Clearer decisions.
A practical guide to working with Untoit Projects. Specific scope, timing and support arrangements are agreed for each engagement.
Getting started
Where should we start?
Choose a recurring task that frustrates the people doing it. Bring a real example, the tools involved and a description of what a better outcome would look like. You do not need a technical brief.
How do you decide what to improve first?
We look at frequency, effort, customer impact, reliability and the work needed to make a change. A smaller, clearly understood process often makes a better starting point than a complicated business-wide rollout.
Can we start with a single workflow?
Yes. A focused scope makes it easier to agree what success means, test with your team and learn before extending the approach.
Scope & delivery
How long does a project take?
Timing depends on the number of systems, data quality, access, decision points and testing needs. We establish those factors during discovery and agree a realistic scope and delivery plan. We do not promise a timeline before understanding the work.
How is the work priced?
An appropriate scope comes first. The estimate should explain the work included, assumptions, third-party costs and how additional requests will be handled. Contact us to discuss your process and the information needed for a proposal.
What does our team need to contribute?
A process owner, access to relevant examples, input from the people doing the work and time to test. You also need someone able to make decisions about requirements and priorities.
Tools & data
Do we have to change our existing software?
Our starting point is to improve how your existing tools are used. We consider replacement only where a clear requirement cannot reasonably be met, and discuss the implications with you.
Can every system be connected?
No. Access, supported interfaces, subscription plans, vendor restrictions and data quality affect what is possible. We assess these before committing to a particular connection.
What if the data is messy?
We identify the information the workflow needs, agree the authoritative record and address the issues that would make automation unreliable. Not every historical record needs to be cleaned before a focused improvement can start.
How do permissions fit into a project?
Access should match the work being performed. During scoping, identify the data needed, who should be able to view or change it and who approves access. Do not share passwords or sensitive customer records through the enquiry brief.
Adoption & support
What happens if an automation fails?
The workflow needs a visible failure path: a useful alert, a responsible owner and a safe recovery step. We discuss monitoring and recovery as part of the design rather than treating success as the only possible outcome.
Will people still be able to intervene?
Where a process needs human judgement, the design should preserve it. We identify review points, manual overrides and what happens when an exception cannot be resolved automatically.
What happens after launch?
Handover and support expectations should be agreed as part of the engagement. That includes ownership, practical guidance, how issues are raised and how future changes are considered.
How do we know it worked?
Agree a baseline and a small number of measures before the change. Review the experience of the people involved alongside speed, quality and the effort required to maintain the workflow.