Start a Project
with ZigNet AI

This section is the basics — who you are and what business you're running. Think of it like the cover page of a project file.

We need this so we know who to send the proposal to, what to call your project, and who our audience is when we start designing. Our AI instantly runs a Companies House check on your business name and SERPER research on your industry — so accuracy here directly improves proposal quality.

This is the most important section. Tell us what you're building, why it matters, and who it's for. The more specific you are, the more tailored and accurate our AI-generated project mandate will be.

The Problem Statement, Success Definition, and Launch Strategy feed directly into the 7 documents our AI team produces. Vague answers produce generic proposals — specific answers produce ready-to-execute plans. Don't worry about being "too detailed" here.

These checkboxes map directly to our development workstreams and scoping model. Every module you select triggers a specific cost and timeline calculation in our AI pipeline. Authentication, integrations, and compliance requirements are the three biggest drivers of project cost — be thorough here.

Dashboard Features and User Volume help us right-size the infrastructure. A system for 50 internal users is architected completely differently from one expecting 10,000 public sign-ups. Tech Preferences lets you steer us toward your existing stack or request recommendations.

This section connects the technical build to your commercial outcomes. The Primary Goal drives how our agents frame the entire proposal — a "Generate Revenue" project gets a monetisation-first architecture; an "Ops Efficiency" project gets an automation-first one.

KPIs and Existing Systems are used by our prospect intelligence agents to validate your brief against real-world benchmarks. Post-Launch Owner changes the technical architecture: a non-technical founder gets a simpler, more managed stack than an internal dev team.

Not every engagement is a full build. This section covers the advisory and consulting services that often precede or run alongside a development project. If you only want a technical architecture review or a go-to-market strategy session — this is where you tell us.

Pain Points is one of the most valuable fields in the entire form. The two most common reasons projects fail are unclear requirements and unrealistic timelines — tell us if you've hit either of these before. Our agents use this to build in specific risk mitigation from day one.

Budget transparency is the single biggest factor in producing a proposal you can actually use. We build at every investment level — but we need to know which bracket we're designing for. A £5K MVP and a £150K platform are completely different scoping exercises.

Hard Deadline changes everything: team allocation, technology choices, phasing strategy, and risk tolerance. Existing Assets (wireframes, Figma files, brand kits, existing codebase) can significantly reduce scope and cost — don't leave these blank if you have them.