Subscription SaaS, B2B operations platforms, audio software. We build all three for clients. We also build all three for ourselves, and one of them bills subscribers every month.
Fourteen systems across SaaS, B2B operations, data infrastructure and audio software. Every one of them is ours. The eight below are the ones worth showing, and what we learn keeping them running is what we carry into your build.
Twelve VST3/AU audio plug-ins. EQ, reverb, compression, tape, delay, filtering, mastering. They share one real-time C++ engine and one control that matters more than the rest: a scrubbable seven-decade timeline. Drag it and every parameter morphs with the era, live.
The line isn’t on sale yet. We’re building a browser demo so you can hear each plug-in before you decide anything.
C++ / JUCE Real-time DSP VST3 / AU Canvas UI
We designed it, built it, launched it, and we still run it. Trade Desk Ultimate is a subscription product with paying customers on a recurring plan we bill ourselves.
We own the full stack: product design, front-end, backend, Stripe subscription billing, tax-compliance configuration, and the day-to-day operations we’re still doing every morning. That last part is the one portfolios skip. So when we warn you about a billing edge case in month three, it’s because it bit us first.
Recorded in the live product
The app subscribers log into, running as they see it.
A multi-surface B2B operations platform for the vending industry: operator portals for fleet and inventory, machine-side software, ordering workflows, and a multi-jurisdictional advertising layer.
Multi-tenant, Postgres RLS, Stripe Connect, real-time. In active development ahead of a supply-chain expansion into Asian manufacturing partnerships. The user we design for is a machine standing in a hallway on a bad connection, and it still has to work.
Interface concepts, not shipped screens. Both apps are mid UI pass right now. These get replaced with recordings off the real thing once it lands, the same way the Trade Desk walkthrough above was recorded.
The data infrastructure, autonomous services and client-side surfaces underneath the headline products. This is where the unglamorous problems live: retries, entitlements, reconnect logic, deletion requests.
React Native and Expo client for the vending platform: multi-operator loyalty balances, machine locator, purchase history, account controls. Account deletion and data erasure went into the first schema, because retrofitting that once real purchase records exist is miserable work.
Touchscreen checkout running on the machine itself. It talks to an on-device Go agent over a typed WebSocket protocol, with a six-state payment machine and reconnect backoff. Networks drop in the places these machines live. The whole protocol is designed around that.
A scheduled Python platform that collects from market data sources on a timer, derives daily and weekly research files, and delivers them to licensed desks through entitlement-gated signed URLs. Each desk gets only what its licence covers.
Seven independent strategy services, each with its own risk limits, decision journal and broker integration, sitting under a shared risk manager and an operator kill switch. Every action is logged and reversible. That’s the only way we’d let software near money.
CoreMello. Production tooling that takes a release from writing through visual production to distribution: asset library, render and generation workflows, and a build order documented well enough that we don’t rediscover it every release.
The React Native app paying subscribers actually open. Strategies, positions, alerts and the research feed on one screen, built to stay readable on a phone at 6am. Sign-in, entitlements and the legal surface are all wired to the same billing account behind the web product.
Fixed scope, fixed price, no hourly meter. Pick a foundation, add what you need, and watch the number move. This is an estimate, not the quote. We confirm the real number on the scope call, and then it goes in writing and stops moving.
Short, fixed-price engagements. A way to find out how we work before you commit to a build. Scope, price and delivery date all get fixed in writing on the scope call.
We read your codebase and send back a written assessment: what’s fragile, what’s quietly costing you money, and the order to fix it in. The document is yours whether or not you hire us for the fixes.
A fixed block aimed at your bug list or that one slow page. You get the fixes, plus regression tests so the same bug can’t come back through the front door.
Subscriptions wired properly: plans, trials, proration, webhooks, dunning, failed-payment recovery. We run this stack in production in our own SaaS, against live subscribers and declined cards.
Your half-finished project put online properly: deployment, domain, SSL, environment config, error monitoring, and backups we’ve restored from at least once.
Connect the systems that don’t talk: scheduled collectors, third-party APIs, validation, and reporting your team can read without you translating it first.
Your algorithm or sound idea running as a working VST3/AU plug-in you can load in your DAW. It’s narrow work. We’ve built twelve of our own on one C++ engine.
Bigger engagements price the same way. Fixed, in writing, before anyone touches a keyboard.
Studio productions are quoted against what they replace rather than by the week, so they sit above the build add-ons. The commercial needs your product photography and a vector logo before the clock starts, and you stay the advertiser of record for what it claims. Anything involving agents is a managed service below, because it carries a monthly fee.
Agents that run one or two of your back-office processes on a schedule, working only on systems you already own. Scoped credentials, written guardrails, read-only by default, a decision log of every action, and a kill switch that stops everything in one click. Anything irreversible waits for a human.
The monthly fee is part of the service rather than an upsell, because an agent that runs on a schedule needs someone watching it. We run seven of these against live markets, each with its own risk limits and decision journal under a shared risk manager. Every action is logged and reversible. That is the only way we would let software near money.
Talk through your workflows →A team of agents that writes, schedules and publishes to your brand accounts, then handles the replies and comments that come back. Every outbound sits in an approval queue until you decide to loosen it. You keep owner-level admin on every account, and a kill switch that stops all of it at once.
The monthly fee is not a licence. It pays for someone to watch the queue, retune the guardrails when a model or an API changes, and answer for it when something reads wrong. We don’t sell this without it. A social media manager runs $3,000 to $6,000 a month, and that’s the honest comparison.
You are the publisher of record. The accounts, the app credentials and the final say on anything sensitive stay with you. We connect through your own OAuth app and never take a password.
Posting and comment replies on Meta. Posting on TikTok. X needs your own paid API tier. LinkedIn is scheduled posting only, because automating engagement there breaks their user agreement, so we don’t sell it.
Not financial services, healthcare or supplements, legal, insurance, cannabis, gambling, or political work. Those carry supervision rules an autonomous agent can’t satisfy.
Plenty of freelancers have built demos. We run our own: a subscription SaaS with paying customers, a B2B platform for vending operators still in build, and a line of twelve audio plug-ins.
A bee arrives at a flower already carrying pollen from the last one. That’s the arrangement here. Most of the architectural calls on your build are ones we’ve already had to live with on ours: billing edge cases, churn, uptime, refund mail from someone who actually paid us. You get the version we landed on after paying for the first one.
Melloworks is a DBA of Futurovend LLC, operating across US and Southeast Asian markets.