Fullstack product build
An idea to a deployed application. API, interface, database, auth, payments, and the boring parts that decide whether it survives contact with real users.
Available for work
Tell me what is standing between your product and shipping.
I build and operate seven products in production — a driver directory taking real payments, a rideshare platform with six portals, an agent company, my own mail system. Same person wrote the migrations, the Caddyfile and the backup that gets restored to prove it works.
Engagements
Four ways people bring me in
If yours is not on this list, say it plainly in an email and I will tell you honestly whether it is something I should take.
AI systems that ship
Model gateways with failover across providers, retrieval, agent pipelines, voice and telephony. Not a demo — something that keeps answering when a provider degrades at 2am.
Infrastructure and deployment
Docker, Caddy, Postgres, Redis, S3-compatible storage, staging promotion, and backups that have been restored rather than merely taken.
Rescue and hardening
An existing codebase nobody wants to deploy. I find what breaks silently, write it down where the next person will read it, and make the deploy boring.
Start here
What the intake asks
Three short steps: who you are, what you need, and — only if it is client work — the two agreements. Joining the community skips the third entirely.
- What you are buildingOne or two sentences. The product, not the technology.
- What is stuckThe thing that made you look for someone. Be blunt about it.
- Where it runs todayA server, a laptop, nowhere yet — all fine answers.
- When it needs to be liveA real date, if there is one.
hello@dectrickmcgee.space
I read everything and reply to anything specific. If it is not a fit I will say so rather than go quiet.