First, tell us about the project

A paragraph or two on what you are trying to build and who it is for. Not what you need doing yet, we will come to that.

First, tell us about the software

A paragraph or two on what it is and what it does for you. Not what you need doing yet, we will come to that.

Do you have a specification?

A spec is simply a written description of what the software should do. If you don't have one, no problem, we write it for you.

Great, upload your specification

Word, PDF, or a link to a doc. Anything that describes what you need.

Tell us what you need, we'll size it

Describe the software or feature in your own words. We turn that into a proper specification for a fixed price, sized small, medium or large.

Do you have the source code?

Before any work or tokens, we need to confirm we can actually access your software. Upload the code, share a repository link, or let us know if you're not sure.

Is it currently working and being used?

This helps us understand whether we're fixing a live system or reviving something that has stalled.

In your words, what happened?

However much or little you want to say. It helps us understand what we are walking into, and it tells us a lot that a list of bugs never would.

What do you need from us?

Pick the closest, then tell us a bit more. You don't need to be technical.

Is there more work after this one?

There is nothing to sign up to either way - we just price things better when we know roughly what is ahead. Buying tokens up front costs less per token, so it is worth knowing.

Where do we send your price?

We'll review what you've told us and come straight back to you. No sales calls unless you ask for one.

Thanks, that's everything we need