I'm Troy. Courage Dev is me.
One developer. I build websites, CRMs, client portals and automations for small businesses, and I do the whole job: the call, the scope, the code, the deploy, and the email you send me six months later when something looks odd.
How I work
I write things down. Scope before price, price before code, and docs as I go rather than in a panic at the end.
I give fixed prices once I understand the job, which is what discovery is for. I'd rather spend a week finding out what you need than three months building the wrong thing at an hourly rate.
Updates come in plain English. You'll know where things are, what I'm stuck on, and what I need from you. If something's going wrong, I'll tell you the day I find it, not the day before the deadline.
Why one person?
Because the person on the call should be the person writing the code. Every handoff between a salesperson, a project manager and a developer loses something, usually the one detail that mattered.
It also means you're not paying for an office, an account team and a pipeline of junior staff. And it means there's a limit to how many builds I take at once, which I'd rather tell you now than discover together later.
The obvious worry with one developer is "what if he disappears?". That's why everything lives in your accounts, the stack is ordinary, and the docs are written for whoever comes next.
Why "Courage"?
Not because building software is brave. It's the small, slightly awkward things: putting prices on the website. Saying "you don't need custom software" when that's true and it costs me the job. Telling you about a problem early. Saying no to work I wouldn't do well. None of that is heroic. It's just easier to skip, and I try not to.
What I won't do
- Hold your code, domain or hosting hostage
- Lock you into a platform only I can work on
- Build dark patterns: fake countdowns, sneaky opt-ins, cancel flows designed to wear you down
- Promise rankings, leads or revenue
- Start work without a written scope
Tools I reach for
PHP and Laravel for back ends. React when a screen needs to be interactive, plain HTML when it doesn't. MySQL or PostgreSQL. Stripe Checkout for payments. The native APIs of QuickBooks, Google Workspace and the rest. Zapier or Make when they're enough. Git for everything. Nothing on this list is fashionable, which is the point: it'll still be maintainable in five years.
Where I am
I work remotely, on Eastern Time, Monday to Friday 9:00–18:00. My mailing address is 108 W 13th St, Wilmington, DE 19801. It's for post, not meetings; everything else happens by phone, video and email.
Wondering if I'm the right fit?
Twenty minutes on the phone usually settles it.