Define the client problem and prepare a small-trial proposal with scope, pricing assumptions, client responsibilities and acceptance criteria. Build a demonstration using NLC, test normal and failure cases and prepare a handover guide with support boundaries.
Use NLC during the practical build. Three months of NLC usage are included free; no prior technical skills are required. After the three included months, continued NLC use costs RM1,000 per month. You can instead stop using NLC and transfer anything you have built using NLC. You handle the transfer yourself. You pay RiseUp nothing to keep your solutions running elsewhere; any hosting or service costs depend on the providers you choose.
During the programme
- A small-trial service proposal with scope, pricing assumptions and acceptance criteria.
- A working demonstration built using NLC and a test record.
- A client handover guide with operating instructions and support boundaries.
Over the next 90 days
- Client discovery records and evidence from an authorised trial, or a clearly labelled practice case.
- A tested solution, feedback, updated handover guide and a recommendation to continue, change or stop.
What successful practice looks like
Show that the build meets a written task and agreed limits through normal and failure-case tests, permitted inputs and human review. Resolve failures or narrow the trial before proceeding. Demonstrate the handover and identify any unresolved dependencies. A practice case is not a delivered client project; securing a client is not a completion requirement.
Bring attempts, feedback and revisions to group coaching. Completion is based on demonstrated skills, application and honest review. Jobs, paid assignments, increased sales and profit are results to pursue, not guaranteed completion conditions.
Explore the two-day syllabus
Day 1: Define the client problem before the solution
Discover the work behind the request
Map the current process and recurring difficulty. Ask for examples, constraints and existing measures.
Output: A discovery guide and current-process map.
Choose a problem AI can usefully address
Compare AI and simpler process options. Evaluate data access, error consequences and human review needs.
Output: A use-case decision record.
Define the limits before making a promise
Define deliverables, exclusions and dependencies. Set acceptance criteria against a baseline.
Output: A scope and acceptance checklist.
Make the proposal assessable
Connect the service to the client problem. State stages, effort assumptions and client responsibilities.
Output: A draft pilot proposal and pricing assumptions.
Day 2: Test a small solution and prepare the handover
Build the smallest useful demonstration
Use NLC to build an automation, web app or another solution for one defined task, using permitted sample data. Document inputs, outputs and human decisions.
Output: A solution built using NLC and a workflow record.
Test failure as well as success
Test normal, incomplete and misleading inputs. Record errors, limits and required human intervention.
Output: A test record and issue list.
Hand over a service the client can operate
Explain operating steps and checking responsibilities. Define support boundaries and a manual fallback.
Output: A handover guide and support boundary statement.
Run a pilot and review the evidence
Plan discovery, permission, testing and review milestones. Define evidence for continuing, revising or stopping the pilot. Prepare the records needed for the 90-day application review.
Output: A pilot plan, evidence log and next-step recommendation. A review template for: Client discovery records and evidence from an authorised trial, or a clearly labelled practice case. A tested solution, feedback, updated handover guide and a recommendation to continue, change or stop.
See the venue, teaching language and programme hours in the attendance section. Confirm the group size for your cohort. Bring a laptop for the hands-on exercises and keep access to it for the 90-day practice period. No prior technical skills are required. The team will explain the tools and accounts to use. Use only material you have permission to share.
Explore an exercise and its review questions
"The Client Takes Over": a peer operates the workflow using only the handover instructions and asks support questions.
Feedback and review: Identify where the client needed help and clarify who owns each decision.
What you revise or apply: Revise handover and support terms before a client trial.
Inspect a worked example: Scope the problem before the tool
Illustrative teaching example. This is fictional, not a participant submission, facilitator feedback record or evidence of results.
- Starting draft
- The client needs an AI chatbot.
- Review question
- Which task needs support? What information may be used and how will a person judge the result?
- More specific version
- Explore a draft-answer assistant for internal FAQs, using approved documents. Test accuracy on sample questions and require human review before use.
Try it: write your own starting statement, answer the review question and choose one action you can check afterwards.
