Enquiry capture
Calls, WhatsApp, email, walk-ins and site visits become structured enquiries with an owner and a next action.
The operating system
From enquiry and quotation to production, installation and financial closure. Explore the architecture and enterprise workflow behind Intellectz.
An order is more than a row in a database. It is a promise moving through people, tools, machines and money.
The Intellectz operating model carries that promise through quotation, design, procurement, production, quality, dispatch, installation and financial closure. Each stage needs the approved inputs and the result of the stage before it.
The products are available through the shared workspace. Enterprise connections are implemented around your systems, rules and responsibilities.
Drawings. Documents. Photos. Conversations. Bring the source and its provenance into the job.
A source document is retained alongside its interpretation. Photos, drawings and commercial documents should remain attributable to the job and the person who supplied them.
Interpret intent, identify missing information and connect each input to the right business context.
Interpretation creates candidates for review. Missing dimensions, conflicting requirements and ambiguous instructions need an explicit resolution before downstream work relies on them.
Use deterministic rules for dimensions, quantities, rates and commercial decisions. Keep assumptions visible.
A model can identify a rate or dimension. The arithmetic and geometry belong in code. Keep units, rounding rules, inputs and output versions available for review.
Call approved tools. Route work to people or systems. Pause at the right approval boundary.
The next action may be a tool call, a draft, an assignment or a request for approval. Execution is constrained by the scope of the workflow and the authority granted to it.
Check the result against the objective. Record evidence. Resolve exceptions before moving on.
Verify the actual result, retain the supporting evidence and handle partial failures. A successful request is not enough if the business state has not changed as intended.
This is the enterprise deployment scope. Availability, integrations and automation levels are agreed during the intelligence audit; the full map is not included in every standalone product.
The enquiry arrives however the customer felt like sending it. It leaves as a priced, specified, accepted order.
Calls, WhatsApp, email, walk-ins and site visits become structured enquiries with an owner and a next action.
Product families — wardrobe, kitchen, door, panelling, upholstery — priced from real recipes, not from a spreadsheet somebody copied.
4,165 rate entries with sources, history and the person who changed them. The price is the company's answer, not an individual's mood.
Every quotation carries its own margin, visible before it goes out rather than discovered at year end.
An agentic follow-up layer that drafts the next outbound message and never forgets a customer who went quiet.
Where most manufacturers lose the thread between what was sold and what gets built.
Wardrobe and wall-panelling planners that turn a measured wall into a validated elevation and a production specification.
DXF and drawing review in the browser, with automated checks before anything reaches the floor.
Dimensions, materials, finishes, hardware and the reasoning behind each choice — attached to the order, not to a designer.
There is one current version and a visible history of every version before it. Nobody builds from last week's drawing.
A drawing goes in. A file your machine can actually run comes out. This is the part nobody else can do.
BXF, DXF and STL converted to machine-ready output for Felder Format-4, H500 5-axis and TPA CN2008 controllers.
Your post-processor, profiled and held at company level — not on one operator's desktop.
Feeds, speeds, tool tables and sheet stock configured per machine during onboarding and validated with a real test cut.
Optimised sheet layouts and setup sheets generated with the file, so the operator gets instructions rather than a puzzle.
Intelligence knows when to proceed, when to ask and when to stop.
6,952 costed BOM lines across product families. The BOM that priced the order is the BOM that builds it.
Available material is reserved the moment the BOM is verified. Shortages surface at order release, not at the machine.
When the requirement is certain and the material is unavailable, the PO is created and sent to the designated vendor.
The agent chases the vendor so a human does not have to remember to.
Purchase orders, bills, invoices and inventory can stay in your existing ERP. The agents read and write over its API — nobody logs in manually.
The floor should know what to do next without being told by you.
Orders scheduled against real machine and people capacity rather than optimism.
Each operator sees the one job in front of them, with the drawing, the specification and the acceptance criteria attached.
Operations sequenced per part, per machine, so the programme and the plan cannot drift apart.
Photo evidence at each stage. An order that cannot prove it passed does not advance.
2,743 hash-chained proof events. Live camera only, zero-trust, and none of it quietly editable afterwards.
The last mile is where reputation is made and margin is lost.
What is loaded is checked against what was made, with evidence, before the vehicle leaves.
Installers, dates and site readiness tracked against the order rather than against memory.
Completion evidence and snag lists captured on site and attached to the order.
The order is not closed when it is delivered. It is closed when it is paid.
The parts of a factory that quietly consume a founder's week.
Onboarding, offboarding, attendance, leave, advances and payslips.
Guard duties, gate records, material-out control and CCTV integration.
Forensic vendor-bill verification with tamper-evident evidence. Scoped during enterprise onboarding.
Discrepancies, collections, GST and payment status against every order.
See the whole business without chasing the whole business.
What is overdue, what is stuck, what is waiting for material, and the one decision that actually needs you.
The numbers that matter, calculated the same way every day, with no one massaging them before the meeting.
Speak to the business. Ask what is holding up an order with the relevant source and context available for review.
Meetings recorded, minuted and turned into owned actions within the agreed workflow.
The daily brief should show where work needs attention and why. An owner should be able to trace a summary back to the underlying order and evidence.
Bring the work that keeps coming back to you.
We’ll map the inputs, decisions, actions and evidence.