Two divisions, one team. Pick the one that sounds like you.
Built on top of the systems you already have, in fixed-scope sprints you own, with working code to test by the second week.
You built it in Lovable, on Supabase, or with another AI tool, and it does what you wanted. Before you put paying customers on it, someone needs to check what the AI wrote, lock down the data, and wire in payments that can be trusted.
“Exceptional. Very creative, and very talented. The only developer I work with.”
“He quickly understood what I was looking to accomplish and not only implemented it but also made great suggestions and improvements.”
“Szabolcs is a GREAT freelancer. What is particular about him is his speed, quality, and initiative to make things better.”
We built a vacation-rental platform's trust accounting. Trusted by the teams behind
Vacation Rental Connect
Airteam
Diobox
Advanced Ads
PlotlyYou grew by acquisition, so you run two or three PMSs and none of them tells you what a single property earns once real costs are in. Every month someone exports them all into a spreadsheet to tell owners what they made. We build the one reporting layer that does it automatically.
ReportingThe owner statement that will not match the year-end totals. The split your management agreement actually specifies, which is not one of the splits the software supports. The short-term and long-term lets that will not combine. Or money that has to move outside US banking rails, into a ledger that is not QuickBooks. We build the one missing piece, alongside the PMS you keep, and tell you honestly if a custom build is not the right answer for it.
Trust accountingEvery tool you have reports backwards. What you actually need is the forward view: what each owner will be owed next month, what is reserved against it, and how much of the cash sitting in your account is genuinely yours, projected from the bookings already on the calendar. The data is there. Nobody keeps the forward view current for you. We build that on top of the ledger you already run.
ReportingAn acquisition or years of growth left you with exports that do not agree: properties named three different ways, fees booked inconsistently, half the history living in spreadsheets. And if you change PMS, the vendor moves your future reservations and archives your past as read-only files. Before a reporting layer, a migration, or an AI feature can work on that, someone has to turn it into one clean model that lives outside any single PMS, so the next switch cannot strand it. We do that as its own bounded, fixed-price sprint, and you keep the result whatever you build next.
Data readinessTrust accounting you do not have, a heavy integration, a feature your roadmap cannot get to without pulling your core team off it. We build it into your platform, as production code you own, which is the one thing a subscription tool cannot be.
Tell us what your platform needsA free fit call, a one-week discovery, then a fixed-scope sprint. You keep the code at every step.
Tell us what your software will not do, and we will tell you whether this is a problem we are the right team for. If a custom build is not the right answer for your situation, we will say so and you will not need us.
We connect to your real APIs and data, produce a confirmed data map, and hand you a firm fixed quote for the build. It is the smallest way to start, and it means the quote rests on your actual data instead of a padded estimate.
A single owned slice, fixed scope and price, working prototype by Week 2 tested against your real ledgers, data, or workflows.
Continue to the full build, integrate deeper, or stop. You keep the code either way. Bigger builds run as a chain of sprints.
This is the same standalone‑then‑integrate model we used for the Housekeeping Checklist, and the same prototype-first method behind every build.
The first four are the things the productized tools structurally do not do. The rest is the depth underneath them.
Projected owner payouts, what is reserved against them, and your own working capital, before the month closes rather than after.
The money history, the owner relationships, and the reporting live in a layer you own on top of the PMS, not trapped inside it. It stays yours through every switch, including the switch to a platform that bundles its own.
We sync to the accounting system you actually use, QuickBooks, Xero, Sage, or a local ledger, not only the one target a US product supports.
Owners open their own view any time. Every serious tool ships a portal now, so the portal is not the point. The numbers behind it, correct to your agreements, are.
Trust accounting, owner disbursement, multi-party and revenue-share settlement, and statements that match the money that actually moved.
Normalized across mixed PMS stacks.
Checkout fires the clean, a finished clean flips guest status, a booking feeds the ledger. Shipped proof: Airteam, a turnover-and-ops orchestration product we built end to end.
Read moreExports from mixed systems turned into one clean, normalized model, as its own bounded sprint before a reporting, migration, or AI build.
Maintenance triage, quality checks, prediction, routing, document and message automation.
You built it in Lovable, on Supabase, or with another AI tool, and it does what you wanted. Before you put paying customers on it, someone needs to check what the AI wrote, lock down the data, and wire in payments that can be trusted.
Fixed-scope work, in your accounts, on the code you already have.
A written report on access rules, auth, exposed keys and data that leaks between users, ranked by risk, then the fixes.
Moving the database, auth, storage and your users out of Lovable Cloud into accounts you own.
Stripe checkout, subscriptions and webhooks handled so that what the customer sees, what Stripe records and what your database stores agree.
Connecting the app to the systems your business already runs, including property-management systems like Guesty and Hostaway.
Monitoring, error handling and a monthly plan after go-live, so the app keeps working while you keep building.
“We built the owner-accounting and reporting core of a vacation-rental platform, in production for 14+ years.”
Flagship build. Per-property ledgers, date-aware splits, payout reconciliation.
Read full case study“Checkout to clean to guest-ready, across the tools an operator already runs.”
10-property STR, Las Vegas, client reached Superhost.
Read full case study“Standalone first, then integrated.”
GPS-timestamped, 10+ properties, 100+ monthly turnovers.
Read full case study“What we build for ourselves.”
Own product, build-in-public.
Read full case studyWe built the trust accounting of Vacation Rental Connect, a platform that has run in production for fourteen years and is live today on a Guesty integration, including the booking-level payout reconciliation that checks what the channel actually paid against what the ledger says it should have. Any developer you hire starts somewhere behind that: a generic agency spends the first weeks learning what a PMS is, and even an STR-aware freelancer starts from scratch on the money-critical parts. We start where they finish.
For over a decade we have built production SaaS used across North America, Europe, and the Middle East, from a vacation-rental platform that has run in production for fourteen years to event platforms trusted by Netflix.
Preparing map...
Tell us what your software will not do, and we will propose a first sprint that fixes one piece of it, owned by you, tested in Week 2.
Free call focused on your operation or your platform, not a generic pitch. If a custom build is not the right answer for your situation, we will say so.