Common questions
The things worth asking first.
Several of these answers cost us work. They are here because you would find out eventually, and it is cheaper for both of us if that happens now.
I do not know what I need. Is that a problem?
It is the normal starting position and it is the first part of the job. Describe what is costing you time, money or customers and we will work out whether the answer is software, a subscription, an integration, or nothing.
What if the answer is that I should do nothing?
Then that is what you will hear, and discovery will have paid for itself by stopping a project you did not need. We would rather be the firm that told you to keep your money and gets called back.
Do you only build custom software?
No, and we try not to. If something off the shelf solves the problem better and cheaper than anything we would write, we will name it and set it up properly. Building is one of five possible answers, not the default.
What does it cost?
Discovery is a fixed fee agreed before it starts. A build is priced before it starts. A monthly fee only exists where there is monthly work behind it.
There is no price list on this site because a number published before anyone has seen your process is either padded or wrong.
How long does something take?
Discovery is short — days rather than weeks. A build depends entirely on what discovery found, which is exactly why the two are separated instead of being quoted together up front.
Do you work in my industry?
Probably. The work is not tied to one vertical, and the problems rhyme more than most people expect: quotes that take too long, information entered three times, customers asking for updates nobody can give them.
We already pay for a lot of software. Will you just add more?
Consolidating overlapping subscriptions is itself something we do. Part of inspecting what exists is finding the tool you already pay for that would solve the problem if it were configured properly.
Is this an AI company?
No. AI is one tool among several and we use it where it earns its place. Plenty of problems are better solved by a simpler system that is cheaper, more predictable and easier for your team to run.
Who actually does the work?
Ryan Conrad. You will deal with the person doing the work rather than an account manager relaying to someone you never meet.
What happens to what you build if we stop working together?
It is yours, including the source. Where a system depends on a third-party tool, you hold that account rather than us, so nothing switches off because we stopped talking.