We helped an agritech company with a messy, complex billing model. Here's what we learned about scaling without code.

As founders, we all start simple. You get your first customers, and billing is a breeze. But what happens when your product needs to support complex, messy plans?

That was the challenge for Farmlogics, a cool agritech company. Their product, Flowforms, is used by farmers to collect data on crop health and soil conditions. As they grew, they had to deal with:

• Usage-based limits: Some clients had a limit of 100,000 submissions, while others needed 500,000.

• Per-user licensing: Each field surveyor needed a license, and the number of users varied by customer.

• Unique enterprise plans: Large clients needed custom, private plans with special features and pricing.

Their team was spending hours trying to manage all of this manually—upgrades, downgrades, and feature access were a constant headache. It was a classic scaling bottleneck.

Here's the key takeaway we want to share:

You don't need a team of engineers to build a custom billing system from scratch. By using the right infrastructure, Farmlogics was able to support all of this complexity without writing a single line of new code for billing.

Our solution helped them create unique plans for each client, automatically enforce usage and user limits, and unlock new features based on the plan. This allowed their team to focus on what they do best: building amazing tools for the agriculture community, not wrestling with spreadsheets.

For us, it was a great lesson in how crucial flexibility is when you're growing, especially for B2B SaaS.

Would love to hear from you: What’s been your biggest "unexpected" challenge after hitting your first 10 or 20 customers?

You can read the full case study here if you're interested in the details: See how we solved this complex billing problem