I connect QuickBooks, Stripe, Twilio and Gmail so your team stops typing things twice, automate the follow-up, and build custom tools when an off-the-shelf app doesn’t fit. One developer, fixed price, everything in writing.
Jerry Mazur, the developer who answers and writes the code
Custom software built to order, and the smaller automations that run every time without anyone remembering.
In detail: Custom software · AI integration · Workflow automation · Twilio SMS · Google Apps Script · QuickBooks & Stripe · All services
You describe what you need in plain words; I build it. A web app, an internal tool, a customer portal, a dashboard, or a complete system for running your business, the way Tessavio Auto runs an auto repair shop. Built in Node.js, TypeScript and PostgreSQL, in accounts you own.
Example: Tessavio Auto, live demo →Connect the programs you already pay for, so a job, invoice or payment typed in one place shows up everywhere it should.
Quote follow-ups and review requests by text or email that stop the moment the customer replies.
Two-way Twilio texting with opt-in, STOP handling and carrier (A2P 10DLC) registration, so messages aren't filtered.
Claude reads and sorts incoming email and documents and drafts the reply. A person approves anything that matters before it goes out.
Stripe payment links, and estimates the customer approves and signs from a text-message link.
A sync that stopped working, a webhook that fails, a spreadsheet script that times out. Small, clearly scoped fixes at a fixed price.
Tessavio DMX
Our product · betaRuns a mobile DJ’s moving heads, bars and uplights from one tablet through a small Wi-Fi DMX plug. The show runs itself on the beat, wedding moments are one tap each, the room is set up once in 3D, and the library knows over 2,400 lights.
What it shows: a real-time product I designed, built and tested on my own wedding rig, from the tablet app to the cloud behind it.
Tessavio Auto
Live demoRepair orders, inspections with photos, estimates the customer approves and signs on their phone, technician time clocks, parts, gross-profit reports, two-way Twilio texting and Stripe payments.
What it shows: I can build and run a complete multi-screen business system with texting and payments, not just one script.
Live-stream control panel
In useBuilt for my own streams: OBS scene switching over WebSockets, track titles straight from the Pioneer decks, donation banners, and a multi-platform relay that reconnects on its own.
What it shows: real-time integrations between separate systems that keep running when a connection drops.
Recorded on a test set, nothing live. DJ footage is licensed stock video (Pexels).
Dental front desk
Video demoBooking by procedure length instead of the half hour, booked-versus-actual chair time, a waiting-room timer, tablet check-in forms with signatures, scanned records with an access log, and a compliance log for the office’s routine checks.
What it shows: a system for sensitive records, built with audit trails, access logging and retention rules from the start.
Shown with a made-up practice and sample patients. No practice is using it yet.
A few lines in writing: what gets typed twice, or what falls through the cracks.
How I would build it, what it costs, and when it is done. No surprises later.
The work is split into small fixed-price milestones, so you pay for one finished step at a time.
Progress as short screen recordings instead of meetings. Test data first, live data only with your OK.
Code, logins and plain-language docs are yours. I stay available for fixes.
Hourly work and small fixes, billed for the time actually worked.
Everything else: a written plan and a fixed price before any work starts.
I run Tessavio LLC from Manalapan, New Jersey. I’m the one who answers your message, writes the code and hands it over. I build with Claude Code every day, including my own automation agents and the MCP server they share.
Evenings and weekends, Eastern time. Same-day replies. In New Jersey I can also set things up in person.
Fair question. Click through the live demo first, then start small: one fixed-price milestone, so your risk is one small step.
You do. Accounts are created in your name, and the code and documentation are handed over at the end.
Keys stay in your accounts or an encrypted secret store, never in code or email. I build and test with sample data and touch live data only with your OK.
No. Everything is in writing, with short screen recordings to show progress. If one short call would help you, that works too.
Everything is documented and lives in your accounts, so another developer can pick it up. I work evenings and weekends, Eastern time, and reply the same day.
A few lines is enough. I’ll reply in writing with how I’d automate it and a fixed price.
I reply in writing, the same day.
info@tessavio.com