Victor T.

Hi! I'm a full-stack developer who ended up specializing in a weirdly specific niche: taking things that almost work – a rough AI idea, a half-finished MVP, someone's vibe-coded weekend project – and turning them into something a real business can actually run on. I take on projects at any stage – from a blank page and an idea, to an existing codebase that needs new hands on it. I've been building software professionally for years, and the work that gets me genuinely excited right now is at the intersection of AI and practical business systems: agents that quietly take hours of manual work off someone's plate, dashboards that finally show a founder what's actually happening in their business, and MVPs that go from "idea on a whiteboard" to "thing customers are using" faster than most teams think is possible. ☑️A bit about how I got here I started out doing classic full-stack work – websites, web apps, the usual. Somewhere along the way I noticed a pattern: the most interesting projects weren't "build me a website," they were "we have this process that's eating 10 hours a week, can you make it disappear" or "we tried to build this ourselves with AI tools and it's held together with tape, can you fix it." That's where I've stayed ever since. ☑️What I actually do → AI agents & automation – I build agents that handle real work: customer support triage, report generation, data entry, internal admin. Not chatbot demos – things that replace hours of someone's week, every week. → Custom business systems – CRMs, internal dashboards, workflow tools built around how your team actually works, not around a template you have to bend your process to fit. → SaaS MVPs – if you have an idea and need to see it as a real, clickable product fast, this is probably my favorite type of project. Weeks, not months. → Rescuing stuck projects – this might be the thing I'm most known for at this point. Half-finished builds, AI-generated ("vibe-coded") apps that worked in a demo and fell apart with real users, code from a developer who disappeared mid-project. I go in, figure out what's actually salvageable, and get it to a stable, shippable state – almost always without needing a full rebuild. → Web & mobile development – still very much in my toolkit when that's what the project actually needs. ☑️How I work I don't start typing code the moment a job is posted. I ask questions first – sometimes annoyingly many of them – because building the wrong thing fast is worse than spending an extra hour making sure we're building the right thing. Once we're aligned, I move quickly, communicate proactively (you'll hear from me before you have to ask "any update?"), and I'm honest early if something in the original plan doesn't make sense anymore. If you're not sure exactly what you need – just a business problem and no spec – that's a completely normal place to start a conversation with me from. ☑️A few results from recent projects ·Rebuilt a client's internal CRM around their actual workflow → 35% increase in operational capacity ·Automated order syncing for a manufacturing client → 8–12 hours saved per week ·Took over a 500-page Figma design that needed real engineering behind it → delivered a working, production-ready MVP on schedule ·Picked up a stalled, partially AI-generated MVP that broke under real traffic → stabilized it into a product the client could confidently launch ☑️When it makes sense to reach out · You have a manual process eating your team's time and suspect AI could kill it · You need a CRM, dashboard, or internal tool that fits your actual workflow, not a generic template · You started building something yourself (with AI tools or otherwise) and it's not quite production-ready · You have an idea and want to see a real MVP fast, not a six-month roadmap · You just want a second opinion before committing budget to a build – happy to do a quick, honest audit first Send me a message with what you're working on. Even if it's half-formed, that's a fine place to start.