Guide Hand
Ask in your own words, follow the hand, then prove the work happened.
The short answer
Guide Hand is an Odoo app for teams in their first weeks on a new database. Someone asks a question in their own words and a hand travels to the exact control, one step at a time, with no Next button to skip. When the showing ends, the server looks for a real record that person created, so readiness rests on evidence rather than attendance.
Last updated
What it is for
Odoo's adoption problem is the first hour. A new starter is dropped into a large ERP and cannot find where to raise a customer invoice or where a payment term lives. Documentation goes stale, videos show a database that is not yours, and the built-in walkthroughs are hard-coded one screen at a time, so they can never answer the question somebody actually has. Meanwhile the rollout gets measured on logins and a training-completed tick, both of which are satisfied by watching. Nobody can say which jobs the team can now do unaided.
- Platform
- Odoo
- Category
- Odoo workspace
- Works with
- Odoo 18 · Odoo 19
- Technical name
guide_hand- Status
- Direct from webbox
- Pricing
- Paid
What is inside it
- 01
The hand
A hand travels to the control and waits for the real click, across screens and page reloads. There is no Next button, because skipping a step without doing it destroys the teaching.
- 02
Grounded in your database
Plans are built from a live catalogue of your own menus, models, fields and buttons, read back through your access rights. The model picks a key; the server compiles it and drops anything not really there.
- 03
Proof it stuck
After the showing, the app steps back and looks in your database for a record created by that person after the check opened. The subject cannot write their own result.
- 04
Team Readiness
One grid: people down the side, jobs across the top, every tick backed by the record that person produced. It prints as a dated PDF, per person, with the evidence underneath.
- 05
Where people get stuck
Every question lands in Walkthroughs with how far the person got. Runs that stop early point at the unclear step, and a Nothing matched filter lists what your team wants and cannot find.
- 06
Bring your own AI
Anthropic, OpenAI, Google, Ollama or any OpenAI-compatible endpoint, including a fully local one. Only your menu structure and one screen's field names are ever sent. Never your records.
What it looks like in practice
-
A first-week user cannot find where to raise a customer invoice
Nothing in the menu tree means anything yet, and the person asks in the words they would use out loud rather than the words Odoo uses.
A hand travels to the exact control with one short instruction behind it, waits for the real click, then moves on across screens and page reloads until the job is done. Phrasings like where do I find skip the planning call and are answered from the route the server already resolved.
Behaviour of the shipped code.
The handGrounded in your database
-
The planner names a control that does not exist here
A model returns a walkthrough whose steps reference controls by key, and one of those keys is invented.
The server compiles each key against the live catalogue and drops anything it cannot resolve, so no hand ever points at it. Because the catalogue is the menu tree the asker's groups can already see, nobody is guided to a button they would be denied either.
Behaviour of the shipped code.
Grounded in your databaseThe hand
-
Somebody finished the walkthrough but their tick is still blank
The job was shown end to end, and the readiness grid still shows nothing for that person against it.
A check goes green only when the server finds a record of the right model, created by that user, after the check opened. Work done beforehand does not count, and work done by somebody else does not count. The person being assessed cannot set the result; the server sets it or nothing does.
Behaviour of the shipped code.
Proof it stuckTeam Readiness
What it deliberately does not do
- It cannot fix your data
- The planner is read-only. It will show somebody where a control is; it will not reconfigure anything on their behalf.
- Full walkthroughs need your own API key
- Navigation questions work with no AI at all, but plans for how do I do X want a model, and you supply it.
- It will not check a navigation question
- There is no record at the end of where is X, so no competency check is offered for one.
- It is not a course builder
- Nobody authors content here. The walkthroughs come from your database, which is the whole point, and it means you cannot hand-write one.
Questions
Can I install this on Odoo Online?
Do I need to pay an AI provider on top of this?
What leaves my database when a walkthrough is planned?
Can somebody edit their own readiness result?
Have something to build?
Tell us the problem. We'll come back with a plan, a price, and who'd actually build it.
- Free scoping call
- Reply within 1 business day
- No lock-in