CASE STUDY — AirBills · FINTECH · B2B UTILITY & PAYMENTS PLATFORM

AirBills: Scaling Payment Automation to $6M ARR.

AirBills needed a B2B utility management platform able to carry $1 million in daily transactions, and needed it inside 30 days. The constraint was not the architecture. It was that a small team had to stand up a product, an operations capability and a payment engine at the same time, on a deadline set by the market rather than by engineering.

BY iAastha Team · AUGUST 2026

FIG·01 — FROM $0 ARR TO EBITDA POSITIVE

Inception $0 ARR

EBITDA +VE $6M ARR

B2B Product Sept – Oct 2023 Build the product and its backend swiftly to test the market.

Tech Operations Feb 2024 Operations capability was the gap. We took it on to acquire and support new product customers.

Product Market Fit Mar – July 2024 PMF reached. Vacasa, AvantStay, PadSplit and Patriot Family Homes acquired as clients.

Optimization, Automation, Growth Ongoing Continuing feature work alongside the founders.

$6M

ARR, FROM A STANDING START

WORKING PLATFORM IN 25 DAYS — FRONTEND · BACKEND ENGINE · API INTEGRATIONS
3 CLIENTS ONBOARDED IN MONTH ONE · $70K PROCESSED
~USD 28,000 / MONTH OF MANUAL OPERATIONS REMOVED
BUILT FOR $1M IN DAILY TRANSACTIONS · 24/7 UPTIME

01 — THE PROBLEM

A 30-day deadline, and four bad ways to meet it

AirBills had to build a scalable B2B utility management platform capable of $1 million in daily transactions within 30 days, then keep shipping features. Every conventional route had a defect the deadline made worse. Hiring one or two developers meant losing weeks to alignment before any code shipped. An agency raised questions of responsibility and accountability. The existing workforce was already stretched, with productivity and maintenance problems of its own. Freelancers introduced IP ownership and platform access risk on a product that would soon move real money.

02 — WHAT WE BUILT

A working platform in 25 days

We took the engagement as a dedicated team operating like an in-house one, and delivered a working version of the platform in 25 days: frontend, backend engine and API integrations. The design target was the transaction ceiling rather than the launch: 24/7 uptime, capable of scaling to $1 million in daily transactions. In the first month the startup onboarded 3 clients and processed $70,000 through it. Feature work continued through several rounds of changing customer requirements rather than stopping at handover.

03 — TAKING WORK OFF THE TEAM

AI applied where the manual load actually was

The operations burden was the second problem behind the deadline. We applied AI to the repetitive work the operations team was absorbing by hand — the bill ingestion, matching and review that scale linearly with properties and billers. That removed roughly USD 28,000 per month of manual workload. It also meant a team that had been running to stand still could take on new product customers, which is what made the next phase possible.

04 — WHAT IT BECAME

From $0 ARR to EBITDA-positive

The engagement ran across four phases. Product and backend were built between September and October 2023 to test the market. By February 2024 the need was operations capability rather than product, and we took that on despite it sitting outside a normal engineering remit. Between March and July 2024 the platform reached product-market fit, acquiring Vacasa, AvantStay, PadSplit and Patriot Family Homes. AirBills reduced burn rate through the partnership, reached PMF in early 2024, and tracked toward break-even by the end of that year at $6 million ARR — with iAastha still working with the founders.

Have a deadline the
usual options cannot meet?

Talk to the team Agentic AI service →

FAQ

Questions about this engagement

Why not hire, or use an agency?

AirBills weighed both. Hiring one or two developers meant spending the deadline on alignment and team-building. An agency raised accountability questions the founders were not willing to carry on a payments product. The existing workforce had productivity and maintenance problems already, and freelancers introduced IP ownership and platform access risk. What was needed was a dedicated team that behaved like an in-house one and could be held to the outcome.

How was a working platform delivered in 25 days?

By treating the transaction ceiling as the design constraint from the first day rather than as a later scaling exercise, and by keeping frontend, backend engine and API integrations moving in parallel with one accountable team. The deadline was 30 days; the working version landed in 25. Feature development continued from there through several rounds of changing customer requirements.

Where did the AI actually get applied?

To the manual operations load, not to the product surface. Bill ingestion, matching and review scale linearly with properties and billers, and were consuming the operations team. Automating that work removed roughly USD 28,000 per month of manual effort and freed the team to onboard new product customers, which is what made the move to product-market fit possible.

What happened after the platform shipped?

The engagement continued through four phases: product build, then operations capability in early 2024, then product-market fit between March and July 2024 with Vacasa, AvantStay, PadSplit and Patriot Family Homes onboarded, and then optimisation and growth. AirBills reduced its burn rate through the partnership and tracked toward break-even by the end of 2024. iAastha still works with the founders.