Start a project
Tell us what you're building.
You'll get a reply within one working day and a call within the week. No drip sequence, no discovery call that turns out to be a sales call.
Starting a project with Shark Labs takes four steps: submit the form below, receive a reply within one working day, take a free 45-minute scoping call that ends with an indicative price range, and — if it's a fit — commission a paid discovery of $400–1,800 that produces a fixed price, a written scope and a delivery date. Discovery is credited against the project price, and you keep the plan whether or not you proceed.
What happens next
- 01
You send this form
Two minutes. Only name, email and phone are required — everything else helps us come to the call prepared, and a blank field has never cost anyone a reply.
- 02
We reply within one working day
A real reply from the person who'd do the work, with either a time for a call or an honest note about capacity. If we're not the right studio, we'll say so here rather than on the call.
- 03
A free 45-minute scoping call
What you're building, what already exists, what 'done' looks like. You'll leave with an indicative range and a straight answer about whether it's worth doing at all.
- 04
Paid discovery, then a fixed price
$400–1,800 depending on scope. We go into the code and the data and produce a written plan: what gets built, what it costs, when it lands. Credited against the project, and yours to keep either way.
Helpful, but not required
- What you're trying to build, in a sentence or two. Plain language is fine — you don't need a spec.
- What already exists: a live product, a repository, a design, a stalled proof of concept, or nothing yet.
- Roughly when you need it, and whether that date is real or aspirational.
- A budget range, if you have one. It saves a round trip and we won't quote to fill it.
- Anything that has already been tried and didn't work. This is usually the most useful sentence in the message.
Project enquiry
Prefer email? hello@sharklabs.tech
What we'll ask on the call
So you can think about it beforehand, or decide the answers make the project not worth doing — which is a legitimate outcome and cheaper now than in month three.
- 01What does success look like, in a number? Not "users like it" — a metric that would move. Teams that can answer this ship better software, because it's the thing that decides what gets cut.
- 02What happens if you don't build it? If the answer is "nothing much", the project usually stalls later for exactly that reason. Better to find out on a free call.
- 03Where does the data live, and who's allowed to see it? On AI projects this is the single biggest cost driver, well ahead of anything about models.
- 04Who owns this after launch? If nobody has a name, that's the most important thing to fix, and it's not a technical problem.
- 05What have you already tried? A stalled proof of concept is usually three to six weeks from shipping rather than a restart, and knowing what stalled tells us which.
What we won't do
- Put you in a nurture sequence. Your details are used to reply to this enquiry and nothing else. No newsletter, no sharing.
- Quote before we've looked. A number produced before anyone has read the code is a guess, and guesses get corrected in our favour later.
- Take work that doesn't fit. If your problem is a data problem, a process problem, or genuinely cheaper to solve by hiring someone, we'll tell you on the call.
- Chase you. One follow-up if we don't hear back. That's it.
If you'd rather not fill in a form
Email works just as well, and a paragraph in an email is often more useful than a form anyway — our contact details are here. Prices are all published on the pricing page if you want to check the range before getting in touch, and the FAQ covers contracts, ownership and payment terms.