Describe your project

If you want software built — a website, a web application, a mobile app, an AI feature, an integration — describe it here. The form opens your email program with a structured brief so you can review it before sending. It is read by a person, and it commits you to nothing.

What makes a brief answerable

The difference between a vague reply and a useful one is almost always the level of detail in the first message. The four things that matter most:

1. The job to be done. Not the feature list — the problem. "Clients book appointments by phone and we lose half of them" tells more than "we need a booking system".
2. Who uses it. How many people, how often, on what device, with what level of technical confidence.
3. A budget range. Not a secret to protect. It determines whether the sensible answer is an off-the-shelf tool, a small custom build or a full product, and those are three different conversations.
4. A real deadline, if there is one. A trade show, a contract date, a funding round. Deadlines change scope more than anything else.

What you should expect from anyone you hire

• A written scope you can read and understand, not a price with no detail behind it.
• Progress you can see — a staging URL, not status emails.
• Clear ownership of the code, the accounts and the domain. It should all be in your name, and you should hold the keys.
• An explicit answer about what happens after launch, and what it costs.
• No lock-in through secret hosting or undocumented systems only they can operate.

Those points apply whoever you hire. If a supplier is vague about any of them, that is the signal to slow down.

Before you send

Run the cost estimator to get a sense of the range, and read choosing a tech stack so the technical conversation starts on even footing. Both are free and neither requires contacting anyone.