Development
Most of my engagements involve building something — a custom web application, an internal tool, a data pipeline, an integration, an automation. This page is the technical slice of that work. Here's what I actually build when the work calls for code.
See the full pictureWhat I build
Four areas cover most of the technical work. Engagements rarely sit cleanly inside one — a real build usually pulls from two or three at once.
Custom Next.js and React builds — the actual product, not a templated landing page. Designed to be fast, accessible, and easy for a non-engineer to update once it ships.
The plumbing that makes a system actually work — auth, third-party APIs, webhooks, and the back-end services that hold a business together when the front door is busy.
Custom reporting that answers the questions your off-the-shelf tool won't. Event tracking wired into a warehouse, dashboards that match how you actually run the business, and the pipelines that keep them honest.
Practical automation built around the work — research pipelines, content generation, internal-ops agents, and customer-facing workflows. Designed so the team using it understands what the model is doing and where the seams are.
Stack and tools
Stack choice follows the work, not the other way around. This is the working set — what I reach for first, and what I bring into engagements when there's no incumbent preference.
Frontend
Backend
Data and analytics
AI and automation
Tools and platforms
How a build runs
No discovery phase, no onboarding tax, no slide deck about what I would do. The first deliverable lands inside the first week — and the architecture has already been thought through end-to-end before a line of code is written.
Diagnose
Map the real work, the real users, and the real bottlenecks. The build brief comes out of this — not a kickoff deck.
Design
Architect the system end-to-end before writing it. Data model, integrations, edge cases, and the seams a future team will have to live with.
Build
Write the actual code. Custom application, internal tool, integration, or automation — built in week one, not after a discovery phase.
Deploy and optimize
Get it live, instrument it, and tune it against real usage. Hand it off with the documentation and tests a working team can actually maintain.
Send me a message and tell me what you're dealing with. One conversation is usually enough to know if I'm the right fit — and if I'm not, I'll usually know someone who is.
or email me directly at contact@corey.consulting