Start with one process
Choose a process that is visible, painful and achievable. One strong journey is better than a broad project that tries to solve everything.
Starter Kit · Module 04
Deliver Greentic
Greentic delivery is about helping customers move from a manual or confusing business process to a guided digital worker that is useful, controlled and ready to improve everyday work.
Successful Greentic delivery starts small, proves value quickly and then expands into repeatable digital worker solutions.The best first engagements are focused, practical and measurable. Partners should avoid trying to automate everything at once. Start with one process, one user journey and one clear business outcome.
Section 1
Delivery principles
Six principles that shape every successful Greentic engagement.
Make the manual pain clear
Understand what happens today: where users get stuck, where staff chase information and where handovers break down.
Design the guided journey
Create a clearer path for the user: the right questions, the right choices, the right approvals and the right handover.
Keep AI under control
Use AI where it helps — understanding, summarising or suggesting — but keep important business decisions within agreed boundaries.
Prove value quickly
Use a small proof of value to show whether the digital worker improves the journey before investing in a wider rollout.
Prepare for scale
Design the first digital worker so it can become a reusable pattern for other departments, industries or customer processes.
Section 2
The Greentic delivery method
A six-step journey from first conversation to a repeatable solution.
1Discover2Design3Demo4Validate5Deploy6Scale
1. Discover
Understand the business problem, the users, the current journey and what success would look like.
Activities
- •Identify the process owner
- •Map the current manual journey
- •Capture pain points and handovers
- •Understand where users get stuck
- •Agree the first journey to improve
- •Define success criteria
Output
A clear description of the current problem and the first journey to improve.
2. Design
Design the guided digital worker journey before worrying about full production integration.
Activities
- •Define the user journey
- •Decide what questions the digital worker should ask
- •Decide what choices or screens the user should see
- •Define approval points
- •Define escalation points
- •Decide where AI can help
- •Decide what should remain human-controlled
Output
A simple target journey showing how the digital worker should guide the user.
3. Demo
Create a compelling demonstration using realistic sample data.
Activities
- •Build a focused demo journey
- •Use realistic names, requests, tickets, invoices or scenarios
- •Show the before-and-after story
- •Show a control point
- •Show human handover
- •Collect feedback from the business owner
Output
A demo that business stakeholders can understand and react to.
4. Validate
Test whether the journey is useful, trusted and valuable.
Activities
- •Run through realistic examples
- •Check whether the right information is collected
- •Review the user experience
- •Confirm escalation and approval behaviour
- •Compare the new journey with the current process
- •Refine the scope before wider deployment
Output
Evidence that the digital worker improves the process and is worth taking further.
5. Deploy
Move from demo or proof of value towards a controlled live deployment.
Activities
- •Confirm production scope
- •Confirm required data sources and systems
- •Agree roles and responsibilities
- •Prepare users and support teams
- •Define monitoring and review points
- •Launch with a controlled user group where appropriate
Output
A live or pilot digital worker supporting a real business process.
6. Scale
Turn the first success into a repeatable solution.
Activities
- •Review results and adoption
- •Identify similar journeys
- •Package reusable patterns
- •Create industry or department accelerators
- •Train customer teams
- •Expand to additional channels or processes
Output
A reusable digital worker pattern that can grow beyond the first use case.
Section 3
First customer workshop
The first workshop should not be a technical architecture session. It should be a business process session. The goal is to agree one valuable journey that can become a demo or proof of value.
Suggested 90-minute agenda
- 1Business goals and current pain15 min
- 2Current process walkthrough20 min
- 3User journey and pain points15 min
- 4Candidate digital worker journey20 min
- 5Success criteria and proof-of-value scope15 min
- 6Next steps and responsibilities5 min
Who should attend
- •Business process owner
- •Operational team representative
- •Customer or employee experience owner
- •IT or systems representative
- •Compliance or risk representative if needed
- •Partner delivery lead
Workshop outputs
•Selected process
•Target user journey
•Current pain points
•Sample scenarios
•Required information
•Approval and escalation needs
•Success criteria
•Next-step plan
Section 4
Process discovery checklist
Use these questions to focus the first conversation on the real business journey.
- What process are we improving?
- Who uses the process?
- What triggers the process?
- What information is needed at the start?
- What information is often missing?
- Which steps are repetitive?
- Where do users get stuck?
- Where do staff need to chase details?
- Who approves decisions?
- When should the process escalate to a person?
- What systems or documents are involved?
- What would a better journey look like?
- What would make the first version successful?
If the process cannot be explained simply, it is probably too broad for the first proof of value.
Section 5
Designing the guided digital worker
Design the digital worker from the user's point of view. The question is not "What can the technology do?" The question is "How should the user be guided to a better outcome?"
Main menu
Give users clear starting options instead of an empty chat box.
Right questions
Ask only for the information needed to move the process forward.
Clear choices
Make the next step obvious through simple choices, forms or prompts.
Business rules
Define what should happen automatically and what requires approval.
Human handover
Decide when a person should step in and what context they should receive.
Outcome summary
Show the user and the business what was done, what is pending and what happens next.
Section 6
AI control checklist
Customers need confidence that AI is helping the process, not running freely without boundaries.
- Where is AI allowed to help?
- Where must the process follow agreed steps?
- Which decisions need human approval?
- Which actions should never happen automatically?
- What should happen when the digital worker is uncertain?
- What should be recorded for review?
- What information should be shown before escalation?
- Who owns the final business decision?
- How will errors or exceptions be handled?
- How will the digital worker be improved after feedback?
AI should make the journey easier, but the business should remain in control.
Section 7
Proof-of-value delivery
A proof of value should prove that the proposed digital worker makes a real process easier, faster or more controlled. It does not need to be a full production implementation.
A good proof of value includes
- One business process
- One main user journey
- Realistic sample scenarios
- Clear before-and-after comparison
- A guided digital worker experience
- At least one control or approval point
- At least one escalation or handover example
- Clear success criteria
- A recommendation for next steps
A proof of value should avoid
- •Trying to integrate every system immediately
- •Solving every process variation
- •Replacing all human judgement
- •Overpromising full autonomy
- •Measuring success only by technical completion
- •Using unrealistic demo data
Section 8
Acceptance testing
Acceptance testing should focus on whether the digital worker supports the business journey correctly, not only whether the screens work.
User journey
- •Can the user understand what to do?
- •Are the choices clear?
- •Is the journey easier than the current process?
Information collection
- •Does the digital worker collect the right information?
- •Does it avoid unnecessary questions?
- •Does it identify missing information?
Business control
- •Are approval points clear?
- •Are escalation rules working?
- •Are boundaries respected?
Handover
- •Does the human receive useful context?
- •Is the summary clear?
- •Does the person know what happened already?
Business outcome
- •Is time saved?
- •Are manual steps reduced?
- •Is the process clearer?
- •Is the customer or employee experience better?
Section 9
Go-live checklist
Confirm these before the first deployment.
- The process owner has approved the journey
- Success criteria are agreed
- User groups are defined
- Support ownership is clear
- Escalation routes are agreed
- Approval points are confirmed
- AI boundaries are agreed
- Sample scenarios have been tested
- Human handover has been tested
- Monitoring and feedback process is in place
- Rollback or pause plan exists
- Communication to users is prepared
For the first deployment, controlled rollout is usually better than launching to everyone at once.
Section 10
30 / 60 / 90-day adoption plan
A simple adoption rhythm for the first three months after go-live.
First 30 days
Stabilise
- •Monitor usage
- •Collect feedback
- •Review escalations
- •Fix confusing steps
- •Check whether users understand the journey
- •Confirm the digital worker is helping the process
Days 31–60
Improve
- •Refine questions and choices
- •Improve summaries
- •Add missing scenarios
- •Strengthen approval and escalation rules
- •Identify additional value opportunities
Days 61–90
Expand
- •Review business impact
- •Package the digital worker as a repeatable pattern
- •Identify similar processes
- •Plan additional channels or departments
- •Define the next digital worker opportunity
Section 11
What successful partners do
Patterns we see again and again in partners who turn first engagements into long-term success.
They lead with the process
They focus on the customer's business journey before talking about technology.
They start small
They choose a focused use case that can prove value quickly.
They show control
They make approvals, boundaries and human escalation visible.
They use realistic examples
They make demos and proof-of-value projects feel close to the customer's real work.
They measure outcomes
They agree what success means before building too much.
They package what works
They turn successful journeys into reusable industry or department solutions.
Ready to turn a demo into a successful first engagement?
Start with one business process, one user journey and one measurable outcome. Prove value first, then scale.