Start a project
Tell us what you are trying to build — and what problem is in the way.
This is the beginning of a project discussion, not a contact form. The more you can say about the problem today, the more useful our first reply will be. If we are not the right fit, we will say so.
What happens next
- A reply from a person who has read the enquiry, not an autoresponder.
- An honest read on whether software is the right answer to this problem.
- A view on scope, sequence and what it would realistically take.
- A clear statement if we are not the right people for it.
What makes an enquiry useful
You do not need a specification. Four things are enough for us to give a genuinely useful first reply.
01
The problem, not the feature list
What is going wrong today, who it affects, and what it is costing you. This is the most useful thing you can tell us.
02
The systems involved
What you already run, what it does, and which parts are the problem. Rough names are fine.
03
What better looks like
How you would recognise success. Not a specification — an outcome. We will help shape the specification afterwards.
04
The constraints
Deadlines, budget reality, internal approvals, regulatory requirements. Better known early than discovered late.
Not ready to scope it yet?
That is normal, and it is what a paid discovery phase exists for. If you know you have a problem but cannot yet describe the solution, say that in the enquiry — we will start from the problem instead.
Not sure whether software is the answer?
Sometimes the right answer is a changed process, a different supplier or no project at all. Tell us what is going wrong and we will say so plainly. We would rather decline than sell the wrong solution.