Quote request
Request a quote.
Tell us what you are building, changing or trying to decide. We will respond with a clear next step and a written proposal where the scope supports one.
A useful quote starts with a defined problem.
We do not send a price from a one-line description. A responsible quote needs enough context to understand the system, the constraint and the level of certainty available. The process below keeps that conversation short and specific.
Send the brief
Tell us what you are building, changing or trying to decide. Include the systems involved and any fixed constraints.
Initial review
We review the brief and respond with clarifying questions or a short call. This is usually within one business day.
Discovery if needed
If the scope is unclear, we propose a focused discovery. It produces the information needed for a responsible quote.
Written proposal
You receive a scope, approach, assumptions, exclusions, timeline, price and payment milestones in writing.
Decision
We answer questions and refine the proposal. There is no obligation to proceed until the written agreement is signed.
What you will receive
- A written scope with deliverables and acceptance criteria.
- Assumptions, exclusions and client dependencies.
- A delivery approach and indicative timeline.
- A fixed price or a capped time-and-materials estimate.
- Payment milestones and the conditions that change the price.
Typical starting points
- Architecture or technical review — one to two weeks, fixed scope.
- Discovery sprint — two to four weeks, fixed price.
- Project delivery — typically eight to twenty-four weeks, quoted after discovery.
- Technical retainer — monthly allocation, usually three to twelve months.
Prefer email? Send the same details to support@nexpathsoftware.com.au and include “Quote request” in the subject.
Thank you.
Your quote request has been received. We will review it and respond using the contact details provided, usually within one business day.
If your enquiry is urgent, call 07 2143 8164 during business hours.
A better brief produces a better quote.
You do not need a specification to request a quote. It helps to know the outcome, the people affected, the systems involved and the constraints that cannot move.
Useful context
- The business problem and why it matters now.
- The users or groups affected, and what they currently do.
- The systems, data sources or partners that must be involved.
- Any regulatory, security, accessibility or procurement requirements.
- The decision date, budget range or delivery window if one exists.
- What success would look like in operational terms.
What happens if the brief is incomplete
We will ask questions rather than fill the gaps with assumptions. If the uncertainty is too high for a responsible price, we will recommend a short discovery engagement. That is a better outcome than a quote that changes materially after the first workshop.
Confidentiality
We treat enquiry information as confidential. If you need a mutual confidentiality agreement before sharing documentation, tell us and we will arrange it before the detailed review.
What we need before we can quote responsibly.
A fixed price is a commitment to a defined outcome. Before we can make that commitment, we need to understand the domain, the systems, the data, the security constraints and the acceptance criteria well enough to estimate the work. A brief that describes only the desired screens is not enough.
If those details are not available, we will propose a discovery with a fixed scope and a written output. That is not a way to delay the project; it is the cheapest way to avoid pricing an unknown and discovering the difference later.
- The business outcome and the people who will use the system.
- The systems, data sources and partners that must be involved.
- The non-functional constraints: security, privacy, availability and accessibility.
- The decision date, budget range and any procurement requirements.
We will also tell you when a quote is not the right next step. If the problem needs an independent review or a support arrangement before a build, we will say so.
Not ready for a quote?
Start with a general conversation. We will help you frame the problem before you commit to a scope.