Talk through what you're trying to fix

You talk, we ask questions, and you'll leave with a plain read on whether custom software makes sense for you. Thirty minutes over video. Most of it is you describing how work moves through your company and where it stalls, while we ask the annoying follow-up questions. Who retypes that? Which report does the owner actually read? What happens when the person on holiday is the one who knows? At the end we tell you what we think. Sometimes what we think is that your current tool is fine and badly configured.

David Verneuille, who founded and runs Black Badger. There's no sales development rep, and no qualifier who books you a second call with someone who knows the answers. David spent years implementing the platforms this company now replaces, so the technical questions get answered in the room. Nothing has to be taken away and checked. If a build follows, he stays on it.

No, and there's a straightforward reason to believe that. We make no money from any software vendor. Nobody pays us a referral fee or a reseller margin, and we carry no quota against any platform we'd have to move. So the answer "keep what you have and fix the configuration" costs us nothing to say, and we say it regularly. If a build isn't the right answer for you, hearing that on a free call beats finding out in month three.

The spreadsheet. Whatever workbook your team actually runs the business in, sitting alongside the platform you pay for, is the single most useful thing you can bring. After that come the platform you've outgrown, a rough sense of how many people touch the process, and the report somebody in leadership asks for that nobody can produce cleanly. You don't need requirements and you don't need a budget number. You don't need to have decided anything at all. If a renewal date is coming up, bring that too.

You get a written summary of what we heard and what we think, whether or not you go further. If a build makes sense, the next step is a written scope. It names the deliverables, the phases, and the assumptions on both sides, all before anything is signed. Larger systems start with a paid discovery so the scope rests on facts and not guesses. Nothing gets signed off a phone call, and there's no drip sequence waiting for you.

We don't publish figures, because the honest number depends on what the system has to do, how many people use it, and how many other systems it has to agree with. Anyone quoting you a price before they know that is guessing. What we can tell you is the shape. We start from what you already pay in licensing every year and scope a one-time build against it. A written scope follows the strategy call, and a firm number follows a paid discovery or our AI-run assessment. Timing is in that written scope too, measured from signing and deposit, because it depends on the same things the number does.

One reply from a person, usually the same business day. A person on our team reads every message. There's no automated sequence behind the form and no lead score. Nobody's going to call you six times. If you want the fastest path, book the call directly on the scheduler on this page. It drops straight into the calendar with no back and forth about times.

No. We're in Clearwater and we serve Pinellas and Hillsborough counties first, but we have clients across the country, and most engagements run over video and screen share whatever the geography. Being local makes an onsite discovery session or in-person training easy to arrange. It's never been a requirement.