
A business problem rarely arrives with the correct supplier category attached. “We need more enquiries” could involve positioning, website usability or search visibility. “We need help with a project” could mean technical engineering work, planning support or people management. Choosing a supplier before describing the problem can lead to a conversation about the wrong deliverable.
For a group of specialist businesses, the first useful step is to identify the outcome and the work that appears to sit behind it. This guide offers a practical enquiry brief, a way to separate related workstreams and questions to ask before agreeing a scope. The examples are illustrative, not descriptions of completed XGEN projects or promises of a combined group service.
XGEN Group’s public portfolio identifies seven businesses: Pro Engineers, Abadi Advisory, Branding Experts, TempWebz, SEOEdge, Bookerr and 3D Print Brisbane. Their areas span engineering, project and people management, branding and digital work, IT, local search, booking software and 3D printing. The current XGEN company directory is the starting point for finding the relevant specialist.
The group’s explanation of how it works distinguishes the parent company from the businesses delivering their own services and products. Use the relevant specialist’s website for a service enquiry and confirm its current offer directly. Common ownership should not be treated as evidence that every project has one contract, one delivery team or one shared support arrangement.
This distinction helps keep the buying process clear. Before accepting a proposal, you should understand which business is responding, what it is providing and which contact will handle questions. If another specialist is needed, ask how that involvement will be scoped rather than assuming it is already included.
Begin with a short account of what happens today. Describe who experiences the difficulty, where it occurs and what evidence you have. “Customers telephone because they cannot identify the correct service online” is more informative than “we need a new website”. The first statement leaves room to investigate whether content, navigation or a more substantial rebuild is needed.
Separate observations from explanations. If enquiry numbers have fallen, state the dates and source of the numbers. If you suspect poor search visibility, label that as a hypothesis until it has been checked. Giving a specialist a conclusion disguised as a fact can narrow the investigation too early.
Also identify what is already working. A business might have a useful booking system but confusing service descriptions. Another might have clear technical requirements but inadequate scheduling information. Retaining a sound component can be as important as specifying what needs to change.
A useful outcome has a recognisable acceptance point. Instead of “improve our digital presence”, a brief might ask for customers to be able to identify the relevant service, read its conditions and complete a tested enquiry route. Instead of “get the project organised”, it might ask for an agreed planning deliverable with defined inputs, review responsibilities and an update process.
These examples are starting points for discussion, not ready-made scopes. A qualified specialist still needs to assess feasibility, dependencies and the right method. Avoid prescribing technical answers before the people responsible have reviewed the evidence.
For measurable business outcomes, distinguish what the supplier can deliver from what the market may do afterwards. A tested page, an agreed report or a configured workflow can have clear acceptance checks. Revenue, search rankings and future customer demand involve additional factors. The brief should not turn an aspiration into an unsupported guarantee.
Use the dominant problem to choose the initial conversation. If the central question concerns an engineering assessment, start by reviewing the engineering business’s published offer. If the problem is how the brand is understood, begin with the branding specialist. If customers cannot find an existing useful service page, review the local-search business’s scope.
When the need appears technical, be specific about the system. A website hosting issue, an email problem and a booking workflow are different subjects even when they all affect the same customer journey. Describe the product, platform or asset involved and the symptom. That gives the receiving business enough information to assess whether the enquiry fits.
If you are uncertain, say so. “We are not sure whether this is a website or booking configuration problem” is a reasonable starting point. Attach a concise description of the failure and ask which investigation should come first. Do not assume one specialist can diagnose or alter another provider’s system without suitable access and agreement.
Suppose an illustrative service business wants to refresh its identity, improve local discovery and simplify appointment requests. These aims are related, but they create different decisions. Someone must approve the brand message. Someone must decide the service-page structure. Someone must confirm the booking rules and operational capacity.
Create a simple workstream list with an owner, required input, expected output and dependency for each item. For example, the booking journey may depend on agreed service names and durations. A website page may depend on the approved customer promise. Search content should reflect services the business actually delivers.
The point is to reveal interfaces early. Ask who will resolve conflicting assumptions, how a change in one stream will be communicated and which business is responsible for each deliverable. Shared ownership does not automatically answer those project-specific questions.
Tell the specialist about fixed events, budget boundaries, existing agreements, staff availability and systems that must stay in place. Explain whether a date is a preference or a genuine external constraint. A campaign launch, a lease deadline and an internal target may require different planning decisions.
List the information already available and its condition. An inventory of existing brand files, website addresses, planning documents or design inputs is useful. Do not attach passwords, private customer records or sensitive technical material to an unverified enquiry channel. Ask how necessary material should be shared securely after the appropriate recipient and purpose are confirmed.
Include the person authorised to answer scope questions and the person who will approve work. They may be different people. If several stakeholders need to review a deliverable, identify them early so a supplier does not mistake an informal comment for final acceptance.
A first enquiry does not need to become a lengthy tender document. The following headings provide enough structure for an initial discussion while leaving room for the specialist to ask better questions.
Send the same factual brief when asking more than one business to discuss the work. Comparable inputs make the resulting proposals easier to understand. If the scope changes during a conversation, update the brief so later discussions do not rely on an obsolete version.
Once a proposed approach emerges, check that the written scope reflects it. Business.gov.au’s guidance on preparing a contract highlights details such as the parties, the work or results, timing, payment and handling changes. The precise terms need to suit the engagement; obtain appropriate professional advice where necessary.
From a practical review perspective, look for unanswered questions. Is content preparation included? Who supplies the underlying information? Does the fee cover one defined deliverable or ongoing support? What happens if an assumption is wrong? Who receives the final files, and in which formats? Raise these questions before the work depends on an informal expectation.
Keep the approved scope accessible to the people doing and reviewing the work. If a later request changes the deliverable, ask for the impact on timing, responsibilities and cost to be recorded. A clear brief is valuable only if the project continues to use it as a reference.
The aim of an initial enquiry is to find the right expertise and establish what needs to be understood next. It does not need to solve every design, engineering or technology question in advance. A clear account of the problem, a realistic outcome and visible dependencies give the specialist a better starting point.
For product or service questions, use the appropriate company in the portfolio. For partnerships and parent-company matters, start through the XGEN Group website. Keeping those pathways clear helps an enquiry reach the business best placed to discuss it without implying that the parent provides every service itself.