001 / Start a project
Tell me about
your program.
Every build starts the same way. Send me a note describing your program, what is not working about the current setup, and what you'd like to fix. I read every inquiry myself the same day, usually within a few hours. Diagnostic calls are free for builds over $2,000.
003 / What happens next
Three quiet things.
Then we talk.
No drip campaign, no automated qualification sequence, no twenty-step intake form. The studio is one engineer. The reply comes from a real person who read your actual note.
I read it the same day
Every note. Usually within a few hours of you sending it. If you sent it on a weekend, by Monday morning.
Same dayI write back personally
Either a few questions about your program or a suggested time for a 30 to 90-minute diagnostic call. No form letters.
One business dayYou get a fixed quote
Three business days after the call, you have a written proposal with a fixed price and timeline. The number is the number.
Three days after call005 / What clients say
In their words.
The diagnostic call alone was worth ten times what I paid. Dusty came in already understanding what a working breeder needs, which is rare. We had a plan I could actually execute within a week.
First developer I have ever worked with who used the words pedigree, hets, and clutch correctly in the same conversation. The records app shipped on the day he said it would.
Three quotes from three agencies. Two were estimate ranges that doubled by the end. Dusty's came in three days, was the number he said it would be, and we shipped on time.
006 / Not ready for a call?
Try a free tool
first.
If you're not ready for a build conversation but want something useful right now, the four free tools take less than five minutes each. No signup, no email gate.
007 / Common questions
A few things people
ask before sending.
Same business day, usually within four hours. If you send a note on Saturday, expect a reply Monday morning. If two business days pass and you have not heard from me, the email got stuck somewhere — please email dmumphrey@builtbydusty.comdirectly and I'll sort it.
Pick the closest match in the Interest dropdown and write whatever you know in the reply email. Most calls start with "I have a program, this thing is broken, fix it." That is enough to start. The Workflow Diagnostic call ($199) is built for exactly this: 90 minutes, written report, no obligation to hire me afterward.
For builds over $2,000, no — the diagnostic is free. For programs that just want a structured working session with a written deliverable, the $199 Workflow Diagnostic call is the right shape. Either way, you'll have something useful at the end whether you hire me afterward or not.
Yes, always. If your project is not something I should take on, I'll tell you that in the reply and try to point you somewhere better. The worst thing I can do for a breeder is quote them on work I'm the wrong person to do.
Absolutely. The three kits in the shop cover most of what small programs need: contracts, deposit agreements, breeding rights, daily SOPs, show and trial prep. Buy once, own forever, no call required.
If you accept, the build starts the following Monday. Weekly written updates during the build. Two scheduled review checkpoints baked into every project. After launch, free changes for 6 weeks (Starter), 12 weeks (Standard), or 6 months (Flagship), and the code is yours from day one regardless.