Tell us about the app or website you need to build

Early conversations are useful before the brief is complete

A good first conversation is usually about the outcome and the uncertainty, not the framework or programming language. If you already have technical documentation, designs or an existing codebase, that context is useful. If you only have the problem and a rough idea of the product, that is also enough to start.

Useful things to include

• What the product or system needs to achieve
• Who will use it and in what environment
• Whether an app, website, prototype circuit/PCB or device already exists
• Any electronics, PCB, sensor, Bluetooth/Wi-Fi or physical-device requirements, plus important integrations or existing systems
• Any deadlines or commercial constraints that genuinely matter
• The part of the project you currently feel least certain about

We can then suggest whether the next step should be discovery, a technical prototype, a defined development phase or a more focused specialist engagement.