Hourly rates - For Profit customers
| Item | Notes | Rate |
| Monthly Retainer | Higher priority on our calendar, best rates. 30 day advanced notice for any changes. | $180/hour, invoiced monthly |
| Prepaid "bucket" | Minimum 20 hours at a time. | $200/hour |
| Regular Hourly Rate | Hour increments, invoiced on completion | $245/hour |
| Emergency Rate | Hour increments, invoiced up front for new customers | $295/hour |
Hourly Rates - Non Profit (501-c3 charity rate)
| Item | Notes | Rate |
| Monthly Retainer | Higher priority on our calendar, best rates. 30 day advanced notice for any changes. | $160/hour, invoiced monthly |
| Prepaid "bucket" | Minimum 20 hours at a time. | $180/hour |
| Non Profit Hourly Rate | Hour increments, invoiced on completion | $220/hour |
| Emergency Rate | Hour increments, invoiced up front for new customers | $275/hour |
Maintenance plans
| Item | Notes | Rate |
| Drupal Protection Plan | Single Site, with dev/stage/production environments | $599/month |
| Drupal Protection Plan - Multisite | Multiple domains, domain access, multi-site configurations | $749/month |
| WordPress Protection Plan | Single site, with dev/stage/production environments | $649/month |
| Server Maintenance Plan | Single server built up with Freelock layout | $350/month |
Case Billing
Freelock is transforming how it does its work. "Hours" are used as a measure for determining rates, and roughly equate to somewhere near the expected level of effort.
However, we don't bill for time spent -- we bill based on cases delivered. Each "case" corresponds to a request. Each case has a "size" assigned that corresponds to hours on your account.
We've found that we can greatly speed up the entire process, and lower the end cost to you, by skipping an estimation step and having you tell us how big each case is. Our project managers can suggest sizing for each of your requests -- however, if it's important enough to need developer input into the sizing, then that becomes a request of its own.
Here are some examples of what we can do with various size cases.
| Size | Hours | Example requests |
| Small | 3 | Most requests are either Small or Medium. Small changes might be a bunch of changes to a header and footer on a site, a new field added to a type of content that appears in a view, changes that involve CSS/HTML, or things that can be done by an advanced site builder. Another common "small" project -- carving up a document with a dozen requests, by a developer who can recommend sizing on each of those requests. |
| Medium | 5 | Simple requests that require custom coding. Pulling simple data from a remote API. Creating a calculated field from underlying data. Creating a plan or prototyping a more advanced feature might also be a medium task. |
| (below are less common) | ||
| Tiny | 0.5 | Single support request that does not involve a release. A simple style change added on to other work. |
| X-Small | 1 | The smallest case size that involves doing a release to production. Can be 2 - 3 straightforward style changes, creating a simple view, quick changes in the UI. Developing a quote -- if you don't want to tell us how big your request should be, we can recommend some budget for a case by doing a "Planning" case -- the deliverable is the plan and recommended budget. Planning cases vary based on the complexity and number of user stories. |
| Large | 8 | More sophisticated custom functionality -- e.g. integrating with SalesForce, setting up a headless widget that not only reads but also writes data back to the site, simple animations. Dialing in responsive behavior for a header/footer on a site. Tracking down a troublesome performance bug. |
| X-Large | 12 | More sophisticated animations. API integrations with multiple dimensions or objects. Plans, reviews, etc. This size is rare -- generally if a request is XL, we are switching over to a planned project, usually starting with a fixed-price Discovery project. |