Inside Ordway Engineering. Ordering the Complexity of Billing

Pablo Cantero
by Pablo Cantero
Nov 14, 2018 11:13:00 AM

Recently announced as one of DC Inno’s 50 on Fire, a “collection of the people, companies and organizations that are heating up D.C.’s innovation economy across six categories,” Ordway is on a mission to eliminate manual invoicing and revenue management workarounds by building the world’s most effective billing and finance platform.

Customers across many industries use Ordway to automate billing and revenue recognition. The platform simplifies finance operations so teams can focus on strategic growth activities. Ordway is efficiently solving the age old problem of getting paid by your customers, by marrying modern technology and talent, with decades of finance, accounting, and billing expertise.

I want to share why Ordway is such a special place for engineers and why our approach to solving engineering problems and designing the world’s best billing architecture works so well for customers.

Flexibility and a modern stack drives Ordway development — Ruby on Rails, React, PostgreSQL

Signing customers, and getting them to pay you for your services, is the heart of every company’s operations. For that reason, Ordway’s billing and revenue automation platform must play nicely within a variety of ecosystems—and those ecosystems can be sprawling. Fast, straightforward connectivity into and out of other platforms is not only a nice-to-have, it’s vital.


Our engineering team designs our service to be as flexible as possible on a Ruby on Rails, React, and PostgreSQL stack. The combination of a modern stack along with a philosophy of flexibility means the core platform is built in a way that can work for all companies. To meet the very specific needs of individual customers, features are designed to be configurable. For example, our customers can configure revenue recognition templates to meet the dynamic needs of their business whether it’s monthly, or even daily revenue recognition rules.

This flexibility is driven by an API-first strategy. To achieve this level of customization, for every feature that is built, we ensure the same experience, regardless of the customer’s entry point and preferred inputs.

Whether using the Ordway application’s web interface, connecting to other systems through the API, or working with .CSV or even Excel files, all of these inputs and outputs work the same.

Making these three methods of interacting with our platform consistent and DRY is fun work for developers.

There is no one size fits all for billing and our platform must go beyond the 80/20 rule

Even within a single company, billing often gets complicated. Our Founder & CEO Sameer Gulati laid out in “Pricing may be simple. Your customer is not,”  how the oversimplification of your pricing and billing model may cause your company to leave money and customers on the table.

For example, Ordway enables our customer ListReports to handle contracts billed automatically on different days throughout the month, and add agents and lenders seamlessly, regardless of billing plan, tier, or contract duration.

The intricacies of building an elegant solution that encompasses all the edge cases related to billing create an exciting challenge for Ordway engineers. Compared to other products, it’s different. Most of my experience is with eCommerce. There is much complexity in eCommerce, though writing something that adds an item to a cart is different than something that needs to accurately generate future revenue schedules, based on complex billing realities. 

Pick process that works

Flexibility permeates everything the engineering team at Ordway does, from our software development approach, to hiring, to how we work together. Examples of this are everywhere, whether it is taking the best aspects of Agile methodology or embracing a hybrid approach to microservices. We’re not looking for any out of the box solution. We pick what we have experience with, and what works the best for us, and do that.

While flexibility is key, we stick to a delivery cycle that employs some hard and fast rules, including:

  • Developers collaborate on every new feature
  • All code goes through code review
  • Product team reviews every new feature and enhancement
  • Feedback collected in development and product reviews is acted upon. We'll update a requirement if that's what is best for the customer
  • Automated tools help ensure code quality and standards

Full stack developers thrive here and we offer more opportunities to learn about all parts of our stack. And equally important, we listen to and solicit input from everyone when designing solutions.

Ordway engineers can be found in Washington D.C., Pittsburgh, and in South America and Europe. We leverage virtual collaboration and productivity tools, and have flexible working hours. There is even an Ordway Slack channel where Brazilian developers are teaching everybody in the company Portuguese and introducing our colleagues to classic and modern Brazilian music.

Many compelling challenges wait on the horizon for the team and we’re always looking for great engineers to join the team. If you want to learn an important technology stack, and contribute to solving important real-world challenges, I encourage you to check out the current openings on our Engineering team.

Topics: SaaS, API, DCTech, careers


Relieve your billing pains

Hear from executives who have been in your shoes

The Ordway blog helps growing businesses understand the best practices around billing and revenue automation.

Topics will include:

  • finance resources for growing businesses
  • spotlights on best practices
  • tips to streamline your billing and revenue processes

Eliminate manual workarounds in order-to-revenue

Discover the Ordway platform

If you are ready to strengthen your sales-to-finance process, our experts are here to help.

Request a demo

Subscribe Here

Recent Posts