The way work works
Your team’s work, answerable from Claude and ChatGPT.
Onboarding, leave, approvals and project status live in wayworks. Ask about them in the assistant your team already uses — answers come from your own records, inside each person’s permissions, and every action is logged.
Early access · one department first
YouWho joins next month, and what isn’t ready for them?
wayworksTwo joiners. One has no equipment request, and neither has a first-week plan. Both managers were asked on the 3rd.
YouRemind the managers and raise the equipment request.
wayworksDone — one equipment request raised, two reminders sent.
By department
Ordinary questions, asked where you already are.
Each one is answered from the records that own it, and anything it changes happens inside the process — not in a spreadsheet beside it.
Who joins next month, and what isn’t ready for them?
Only the people this manager is allowed to see are in the answer.
What are we approving this week that’s over the usual amount?
The outlier goes to a second approver, with the policy line attached.
Is anything on the client project actually blocked?
A chase is drafted for a person to send; a ticket opens where the work is.
Which orders are waiting on us rather than on a supplier?
Reassigned inside the process that owns them, with the reason written down.
How it works
Ask. Don’t navigate.
Nobody keeps twelve tabs open because they want to. They keep them open because the answer is spread across twelve places. Put the work on one base and a question can be asked once, in plain language, and answered with the organisation’s own records behind it.
- 01The ask
Someone types a sentence in the assistant they already have open. No new window, no syntax, no menu to learn.
- 02The connection
The wayworks connector carries it to your space — built on an open standard, not a scrape, and it can only do what it is allowed to.
- 03The work
Your process runs: the item moves, the approval routes, the document is filed where that kind of document belongs.
- 04The record
Who asked, what ran, what changed and when — kept beside the work rather than in a chat thread somebody has to find later.
Trust
Intelligence without governance is just automation with risk.
Each assistant connects as its own agent, with named capabilities and a list of people it may act for. Every call is checked against those limits and written to an audit log, and an agent can never be given more than the person who created it had to give.
What’s underneath
One product here. One foundation below it.
wayworks is the part you use. DebugInit is the foundation it stands on — a shared base for identity, permissions, workflow, audit, documents, search and intelligence, so the work layer inherits one architecture instead of assembling one. The same base sits under everything else the ecosystem builds.
the product has a name.
so does the ground
Core Platform
Identity, permissions, workflow, audit, documents, search, notifications, APIs — built once, shared by everything above.
Internal Tools Studio
Forms, roles, rules, dashboards and your own terminology. Your operating model becomes the software.
Business Foundations
Twelve reusable operational blocks, configured around the organisation rather than sold as twelve products.
Early access
Your company already has a space.
Early access starts with one department and one real process, measured before and after. Tell us which one you’d move first.