Get a quote
Start with a useful project brief.
A few practical details give the team enough context to ask better questions about priorities, workflows, systems and timing.
BRIEF / DESIGN / NEXT STEP
A useful first brief
Tell us enough to avoid the generic pitch.
- Organisation or project type
- Current operating context if known
- Relevant documents or screenshots if available
- Priorities, constraints or change goals
- Preferred timing
Project brief
Start with the business, not the brochure.
Send the project context, project type, current operating situation and what you want the work to achieve. Add relevant documents or screenshots when you have them.
Location
Current state
Inputs / systems
Change goals
Prefer email? Use the address configured as this WordPress site’s Administration Email Address.
Before you buy
Questions worth asking before anyone starts the work.
How do you decide how many workstreams I need?
Start with consumption, usable team capacity, orientation, shading and how the building is used during the day. A useful design is not simply the maximum number of workstreams that fit.
Do we need new technology?
Not automatically. New technology makes sense when the operating model, business goals and delivery constraints justify it. The system should support the work, not become a separate project.
Can the system be prepared for an change or heat pump later?
That future demand belongs in the design brief. Platform choices, team capacity, workflow dependencies and change strategy can all be considered before implementation.
What should a quote actually show?
At minimum, the proposed scope, assumptions, responsibilities, measurement approach and any project-specific commercial or performance terms that have been verified.