Our Pricing Philosophy

This is part of our How We Work series of blog posts. Today, we’re talking about our pricing philosophy.

Written by
Ben Wald
May 22, 2017
Filed under:

This is part of our How We Work series of blog posts. Today, we’re talking about our pricing philosophy.

We'll answer several key questions, including: 

  • How much is this going to cost?
  • What are your rates?
  • What is a "billable hour"?
  • How long will it take?
  • When should we talk about my budget?

Clarity is power

With dozens of approaches to consider, designing and engineering custom technology solutions means navigating myriad tools, platforms, languages, and frameworks, each with pros, cons, and unique trade-offs. If you’re thinking of hiring us, it’s probably because we're good at this.

Since our goal is to maximize the value you can create and the return on your investment in your technology platform, it is critical to have a clear understanding of your budget so we can consider your constraints and goals as we recommend the best path forward.

Our goal is not to capture the most money we can out our relationship — it's about getting the most value out of the money committed, even if that means not spending it with us. This is only possible if you let us help you think through the trade-offs between the short term options and long term goals.

We will be a great fit if you have a clear business objective, value you want to create and domain expertise on how the solution should behave from a market adoption standpoint — and you want a trustworthy technology partner to help make it happen.


Each iteration is one week long, and we bill at $250 per hour, per engineer, which translates to a target of $7,000 per week. Project management is provided at a flat rate of $3,500 per week for a part-time Product Manager or $7,000 per week dedicated Product Manager. We typically work four days a week on client projects and reserve one day for internal meetings and projects. Our rate includes devops support and all tools and services we use in our typical workflow.

What is a "billable hour"?

Every team member records where they spend every minute of their day. You only pay the billable rate when our team members are actively working on delivering features and functionality for your application. We keep track of every hour spent on your application and report every week on how we are tracking on the budget and schedule. We'll also happily provide a budget report at any point in time. You'll have a dedicated place within our time tracking and invoicing tool to manage invoices, review line items, and keep up with how your money is being spent.


At the beginning of each engagement we build the Pivotal Tracker board and development roadmap together. This allows us to prioritize and confirm scope, timelines, and the resources we have scheduled. We equate one story point to a seven-hour day for each team member who is working on your project — and your project only.

Once we establish a working velocity, we'll have a better understanding of our delivery pace, and can adjust scope to meet the targeted budget or timeline. We'll work with you during our weekly Iteration Planning Meeting (IPM) to adjust the delivery roadmap and discuss any trade-offs that are necessary to maintain alignment with budget and timeline.


We understand every project has a budget, and we do our best to plan for and accommodate budget constraints. Typically, when beginning a project and outlining a product development roadmap we work together to identify a budget target and a budget cap. We like to have these conversations as early as possible in the process. 

Our goal is to reach the milestones we outline before we reach the budget target amount. The budget cap, which is usually 20-30% above the target, usually represents the maximum amount you can afford. This is either based on annual budgeting, budget allocations for the project or simply the amount of investment capital available for the project. Understanding this number gives your Product Manager the information they need to recommend trade-offs during the process and ensure we deliver the best solution before resources are expended.