Custom development is our core business, which means most of the work we take on starts with something that does not exist yet. That also means the first conversation has to establish whether the idea is a product we can build, or a set of requirements that need to be separated before anyone quotes.

Five checks, in this order

  1. Is the use clear? A unit for seasonal guests, a reception building and a staff block have different requirements. If the use is still open, we help define it before developing a layout.
  2. Can it be transported? Dimensions, weight and route constraints are checked early, because a design that cannot pass the last bridge is not a design.
  3. Can it be built in our system? Some structures suit a workshop environment and some do not. We are honest when a concept would be better delivered by site construction.
  4. Can it be maintained? Service access, replaceable surfaces and drainage are reviewed with the operator in mind, not only the buyer.
  5. Does it duplicate a family? If an existing unit direction is close, adapting it is usually faster and cheaper than starting from zero.

Requests we decline

We decline work for reasons that are consistent, even if they are not always welcome:

  • The site and the intended use are both undefined, and the request is effectively a request for a catalogue.
  • The requirement is to copy a competitor’s product exactly, including its structure, without any engineering review.
  • The specification contains performance or certification claims that we cannot verify or support.
  • The brief is price-only, with no scope, quantities or delivery expectations to price against.
  • The project needs a type of construction outside our capability; in that case we say so rather than subcontract the answer.

What follows a review

After the checks, three outcomes are possible. If the request fits a unit family, we move to configuration and a standard proposal. If it needs development, we scope the development steps: feasibility, scheme and engineering, validation where justified, then manufacturing. If it does not fit, we explain why and, where we can, point to the part of the brief that needs rethinking.

Why this matters to clients

A development project that starts with an over-optimistic yes usually ends with a redesign in production. The review is not a filter designed to slow things down; it is the point where the project either becomes buildable or becomes cheaper to change.

Send a brief through the enquiry form and the review is the first thing that happens.