Saifullah S.

I work directly with the Founders and design the parts that usually break, then build the whole product myself. Most of the trouble I see isn't in the features. It's in permissions, billing, background jobs, integrations, and the AI step that does something it shouldn't. That's the part I design first. The rules I build by: - Design first. You get a written plan with the data model, failure modes and running costs before any code. - Every customer's data isolated twice, in the app and with Postgres row-level security, so one bug can't leak another customer's data. - Credentials encrypted with AES-256-GCM, and server-side fetches protected against SSRF. - The model decides, the code enforces. An AI agent never takes an action your rules don't allow. - Built for failure. Queues survive crashes, jobs retry, duplicates get caught, and backups get restored in a test, not for the first time in an emergency. - It's not done until it's tested and load-tested. - Boring, documented tech over clever tech, so the next developer can pick it up. What I take on: - New SaaS platforms and MVPs on Next.js, Node.js and PostgreSQL: multi-tenant data, auth and roles, Stripe billing, queues and admin. - Existing products that keep breaking: I find the architectural cause, fix it and extend the product without taking production down. - AI agents and LLM features on OpenAI or Claude, plus the APIs, webhooks and n8n workflows that connect your tools. Where I've built: lead-generation platforms, call-center and voice AI systems, marketplaces, e-commerce automations and ad tracking for agencies. How working with me goes: a short plan first, then milestones you can test, updates without chasing, a report at every milestone and a walkthrough at handover. I'll tell you straight when something is a bad idea. Questions clients usually ask: - Hourly or fixed price? Both. New builds usually go fixed price per milestone after the written plan; ongoing work is hourly. - Can you take over code someone else wrote? Yes. I read it, document what's there and fix what's dangerous before adding features. - Time zone? I'm in Islamabad, Pakistan, and I work into the night, so I overlap with US mornings and UK and EU working hours. Stack: Node.js, TypeScript, Python, Next.js, React, PostgreSQL, Redis, BullMQ, Prisma, Docker, Stripe, OpenAI and Claude APIs, n8n. Send me what you're building or what's breaking. I'll reply with how I'd structure it and a realistic first milestone.