Skip to Content

Feature Request

A new capability, or a change in how something works. Please answer in plain business language: the tech team will review feasibility, then write the detailed requirement and test cases and confirm them with you before anything is built. If something is simply broken, use the Issue form.

1. About you

Your manager or department head, if any.

2. The problem

Describe the problem first, not the solution.

One line. Example: "Let dealers see their order status without calling us"
What is hard, slow, error-prone or impossible today? Who feels it?
Excel sheet, WhatsApp, manual entry, nothing at all ...
Roles and rough numbers. Example: "8 designers, about 20 times a day"

3. What you want

What should the person be able to do, and what should the system do in response?
Start to finish with real data: a real customer, order, quantities and amounts. Step 1 ... Step 2 ...
Pricing, GST, discounts, approvals, limits. What should happen in the odd cases (cancelled order, missing data, partial payment)?
Other teams, documents and reports that change: quotation, drawings, sales order, invoice, payments, stock, dealer portal ...
Which roles can use it, which can only view, who must not see it.

4. Done and value

Three to five checks in the form "When I do X, I should see Y". These become the test cases.
Time saved, errors avoided, revenue gained. Rough numbers are fine.
Launch, audit, customer commitment ...

5. Mock-up (optional but very helpful)

A sketch, a screenshot with notes, a sample Excel, or a clickable prototype built with Claude or ChatGPT.

Submit Feature Request