Describe the stuck process, not a list of features

Start with one real example

Walk through the last order, enquiry, approval, service request, booking, claim, or report that caused trouble. Where did information arrive? Who copied it? What did they have to check? Where did the customer wait? Which step depended on somebody remembering what to do?

Include the operating context

• The people who use the process, including customers, staff, suppliers, and administrators.
• The systems already involved, such as email, spreadsheets, accounting, CRM, e-commerce, document storage, or an older internal application.
• The records that must remain accurate and the system that should be treated as the source of truth.
• Australian locations, time zones, terminology, currency display, tax inputs, accessibility needs, privacy questions, and support expectations that may affect the work.
• Deadlines, seasonal peaks, contracts, renewals, or other events that make an interruption expensive.

Define a result people can recognise

“Make it efficient” is difficult to test. A clearer result might be: customers can see job status without calling; an approved order reaches accounting without re-keying; staff can find the current document; a failed payment creates a visible follow-up; or a manager can see which requests are waiting and why.

Decide who can say yes

Name the person who approves scope, content, access, privacy and security decisions, and the final release. If an Australian adviser must confirm tax, legal, accessibility, or regulated-industry requirements, identify that dependency early rather than discovering it during launch.

Do not send passwords, API keys, private records, regulated data, production exports, or confidential credentials in the first message.

Email: faithforgelabsllc@gmail.com Phone: 404-939-0637