Software problems, found and fixed.
I'm Joshua, a software consultant in the Greater Baton Rouge area. There are two ways to work with me: a review that finds what's wrong with your site or system, and a focused block of engineering to fix it.
The first conversation is free, and there's no hard pitch.
How it works
A review to find it. A block to fix it.
The Review
A focused review that answers one question. Pick the one you're worried about:
- Security: Am I leaking data I shouldn't be?
- SEO: Do search engines and AI engines trust me?
- Accessibility: Are customers struggling, and could that get me sued?
- Legacy Assessment: Is my aging app worth saving, and how?
This isn't a 1,500-page automated scan. I look for the problems that repeat on every page, because fixing the template fixes them everywhere. You get a written report and a prioritized list.
The Block
10 hours of senior engineering, aimed at one specific thing.
Buy one when you need it. Big jobs like modernizing an aging system run as a sequence of blocks: one slice at a time, and you can stop after any of them.
- You bring a specific problem. I scope it, build it, and ship it.
- You work directly with the developer writing the code, with no account manager in between.
- I'm local to South Louisiana, and I work remotely with clients everywhere else.
The review finds the problems and the block fixes them. What you paid for the review comes off your first block.
Book a free consultWhat a block is for
What people spend a block on.
A block is ten hours of engineering pointed at one problem. Here's where most of them get spent.
Legacy modernization
For the system that's old, slow, and expensive to host. I bring it up to date in slices rather than one giant rewrite, so it keeps running the whole way through.
Process automation & AI
That task your team does 40 times a day? I build an automation to handle it, with a dry-run mode and human review so it can't break production without anyone noticing.
Close the gaps
The security, SEO, and accessibility problems your review turned up, fixed and verified. I ship the fixes myself instead of handing you a report, and your review fee counts toward the block.
Integrations & glue
Get two systems talking to each other: payments, ERPs, calendars, and whatever API sits between them.
Why not later
The longer it sits, the more it costs.
None of these problems get better on their own. Here's what waiting on each one costs.
Exposure doesn't fix itself
Leaked keys, open admin panels, customer data in the page source. All of it sits in the open until someone finds it, and you don't get to pick who.
You can't see the traffic you're losing
If search engines and AI tools can't read or trust your site, the customers they would have sent you end up somewhere else, and nothing tells you it happened.
A demand letter costs more than the fix
Website accessibility complaints are a growing, well-funded cottage industry. Closing the gaps costs a fraction of answering one.
Old systems only get more expensive
Hosting costs creep up, changes take longer, and the migration you'll eventually need gets bigger the longer you wait.
Who I work with
Operators whose software is running the company.
The sweet spot is a company that runs on an in-house system: billing, scheduling, dispatch, compliance, the customer portal. It still works, but it's aging, and everybody knows it. I've spent six years as the only engineer inside companies like that, so I price and ship like one.
- Your problem, start to finish. You bring the problem. I see it through from scoping to shipping, and I stay on it after launch.
- A real person nearby. I'm local to South Louisiana, so there's someone you can actually call and meet face to face.
- No agency in the middle. You work directly with the developer building it, so decisions get made in one conversation.
Industries I've shipped into
- Distribution & wholesale
- Compliance & regulated ops
- Marketplaces & multi-vendor
- Retail & POS
What clients tend to bring me
- · An aging in-house system the team has outgrown
- · A new product to ship before someone else does
- · An integration or automation that has to hold up in production
- · A security finding that needs to be fixed quietly
Selected work
What I've shipped.
Each one starts with the problem it solved.
Case study · 01
CookJunkie
A WordPress-to-Next.js migration of a 15,000-recipe site, with AI-repaired legacy data, AI-assisted recipe authoring, a social cooking community, and a Stripe + Lulu print-on-demand cookbook business on top.
Case study · 02
Security Review
A zero-knowledge review of a mid-size B2B distributor that turned up 14 unauthenticated dashboards, customer financials, and wholesale pricing on roughly 45,000 products, all served without a login.
Case study · 03
TutorTab
A Stripe Connect platform where independent tutors accept their own payments and parents run autopay across every tutor. Magic-link sign-in, two-way Google Calendar sync, an automated reminder cascade, and the same engine white-labeled as TrainerTab for personal trainers.
Case study · 04
Vorbiz
A native iOS + Android POS for market vendors with offline-first multi-device sync, QR-based sale capture, bulk inventory import from CSV or a Google Sheets URL, and sales-tax + revenue reports they can hand to their accountant.
↓ Next step
Not sure where to start?
Start with a review and you'll get a straight answer about where you stand. The report is yours to keep either way. Or just tell me what's stuck. The first call is free: 30 minutes, and nobody tries to sell you anything.