- Who it is for
- Owners and teams across industries, from solo operators to larger organisations, who spend time chasing information, repeating admin or copying details between systems.
- What you get
- A clear scope, honest advice and a team that knows how to use what we build.
- What it isn't
- Error-free automation. Review steps reduce risk; they do not make a system error-free, so important decisions stay with your people.
A clear path from idea to everyday use.
| Who it is for | What you get | What it isn't |
|---|---|---|
| Owners and teams across industries, from solo operators to larger organisations, who spend time chasing information, repeating admin or copying details between systems. | A clear scope, honest advice and a team that knows how to use what we build. | Error-free automation. Review steps reduce risk; they do not make a system error-free, so important decisions stay with your people. |
The four stages
Ongoing support is agreed separately, with its own scope.
| What we do | What you get | What we need from you | |
|---|---|---|---|
| 01Understand the work | We look at the task, the systems involved and what a worthwhile improvement would look like. | A shared description of the work and what better would mean. | Someone who knows the process. |
| 02Agree the scope | We write up what we will build and what it will cost. | A written plan, a fixed build price and an explanation of expected running costs. | A decision on the plan. |
| 03Build and test | We develop the agreed workflow and test it with your team, including review points and what happens when something fails. | A tested system with its review points agreed. | Access to the agreed systems and time to test the result. |
| 04Train and hand over | We walk your team through it and document access, known limits and the support arrangements agreed with you. | Practical instructions your team can use. | Time for the walkthrough. You do not need to know how to code. |
01Understand the work
- What we do
- We look at the task, the systems involved and what a worthwhile improvement would look like.
- What you get
- A shared description of the work and what better would mean.
- What we need from you
- Someone who knows the process.
02Agree the scope
- What we do
- We write up what we will build and what it will cost.
- What you get
- A written plan, a fixed build price and an explanation of expected running costs.
- What we need from you
- A decision on the plan.
03Build and test
- What we do
- We develop the agreed workflow and test it with your team, including review points and what happens when something fails.
- What you get
- A tested system with its review points agreed.
- What we need from you
- Access to the agreed systems and time to test the result.
04Train and hand over
- What we do
- We walk your team through it and document access, known limits and the support arrangements agreed with you.
- What you get
- Practical instructions your team can use.
- What we need from you
- Time for the walkthrough. You do not need to know how to code.
Control and information
| What it means | |
|---|---|
| 01Your business controls the setup | We agree which accounts your business will hold and what access Ignis needs during the build and any ongoing support. |
| 02Access matched to the work | We define the required permissions and check them before connecting business information. |
| 03Provider settings explained | We review the relevant training, retention and access terms for the services in your proposed setup. |
| 04Hosting requirements considered early | Tell us if information must be stored or processed in a particular location. We check which parts of the proposed setup can meet that requirement. |
| 05A record your authorised team can use | We agree what actions and approvals are recorded, who can see them and how long records are kept. |
01Your business controls the setup
- What it means
- We agree which accounts your business will hold and what access Ignis needs during the build and any ongoing support.
02Access matched to the work
- What it means
- We define the required permissions and check them before connecting business information.
03Provider settings explained
- What it means
- We review the relevant training, retention and access terms for the services in your proposed setup.
04Hosting requirements considered early
- What it means
- Tell us if information must be stored or processed in a particular location. We check which parts of the proposed setup can meet that requirement.
05A record your authorised team can use
- What it means
- We agree what actions and approvals are recorded, who can see them and how long records are kept.
Questions
How long does a build take?
Timing depends on the workflow, the systems involved and how ready the information is. We agree milestones before starting and identify what could delay them.
Who owns the system, and can we change providers later?
Our default is to build in accounts your business controls, with agreed documentation and access at handover. We explain export options, ongoing dependencies and any limits before you commit.
What support do we get after launch?
We provide the agreed walkthrough, operating instructions and handover. Ongoing maintenance and improvements can be covered by a separate retainer that sets out support hours, response expectations and exclusions.
Bring one task. We will look for the first step.
Tell us how the work runs today. We will discuss whether there is a useful next step, and what it would take.