These are the tools I use on most projects. Each one shows the version and where it runs.
All four are real builds. None are publicly deployed right now.
Case studiesStealthyBatProxiesResixChatBox
Fixed scope, fixed price. You own the code at the end. Most clients start with the internal ops tool.
Online storefront
A storefront built around your catalog. It follows your product structure and your checkout steps, and includes an admin panel your team manages. Cart, payments, tax, and shipping are handled on the backend.
Self-serve returns
A portal where customers file their own returns. You approve each return in one click. The refund, restock, and status emails are then handled automatically.
Operations in one place
A single tool for running your operation. It replaces a setup spread across spreadsheets, a payments dashboard, and multiple browser tabs. Includes user and admin views, a balance ledger, crypto and card payments, a live event feed, and the automations that connect them.
Connected to your systems
A bot connected to your systems. It handles paid roles, support tickets, moderation, and scheduled jobs. It connects to your database and Stripe, so actions in Discord update your other systems in real time.
Marketing site
A marketing site built to your design. It loads fast and is built for SEO. A CMS lets your team edit copy and images. You own the code and can host it anywhere.
Auth, billing, email, admin
The standard parts every SaaS needs: authentication, subscription billing, transactional email, and an admin console. I build this layer so you can focus on the product itself.
Email, Telegram, or the Discord — whichever works for you. I read these myself and usually reply within a day.
