Thinkbean is a Boston-area based, Drupal-only development company with a very strong guiding, overarching principle: Build a purposeful web. We like to think of our work as building sites that do something, not just say something. That means we enjoy taking an integral role in working with clients to formulate and crystallize objective, clear and concise business goals. Then, architecting and building the application to achieve those goals.

As is probably the case with development shops of any sort, we’re very proud of our programmers and we believe they are some of the most capable people in the business. As is probably not the case with many development shops, our belief is evidenced by the fact a significant amount of our business comes in the form of ‘rescue projects’. That is, many of our clients initially come to us because their then-current vendor’s skill set has been exhausted and experts are needed to bring the project to a successful completion.

We don’t try to be all things to all clients. We are one thing - Drupal experts. Many development shops service multiple platforms. We don’t. We believe Drupal projects require Drupal experts if they are to be completed properly, efficiently and successfully. We’re very proud of the fact Thinkbean is always the last stop for our clients. Never do our clients have to go to other Drupal development shops to get the service they need. We aim to keep things that way.

Get to the nitty gritty

View Our Case Studies

Recent Blogs

No one wants to be the person who invested hundreds of thousands of their company’s dollars into a new website, app or digital asset, and then have it fail to do what it was built to do.

Even fewer people want to be the ones to then tell their management team that the project needs even more investment – sometimes as much as the initial expenditure – to fix the problems; or worse, start over.

In the web industry, we call this a rescue. They are every bit as horrible as they sound, but there’s good news. They can be prevented.

Elasticsearch will take any data you throw at it, but without a predefined index, it will try to figure out the data type on its own, which can result in both inefficient storage and querying. It can also limit ways to use your data in some cases.

Let's consider http status codes for example. These values are always integers, however Elasticsearch will treat them like text unless you explicitly define your index.

We started offloading web logs from Acquia into Elasticsearch, and let me tell you, it's been amazing!

Imagine being able to query your apache access log for https status 500 errors that occurred in the last 4 hours; or retrieving the most common 404 paths. Maybe you're more visual and want to see pie charts of bytes downloaded per country, or histograms of status codes per half hour. Perhaps you want to trace the footprints a certain IP address made on a particular domain, then across multiple domains.

Let's Build Something Together

Request A Quote