Boston, Massachusetts
Start a conversation with thoughtbot
Tell us what you're working on and we'll get back to you, usually within a couple of business days. A rough description is enough to start: what you're building, who it's for, and what's blocking you.
Before you write
What to include
The most useful messages cover four things. If you don't have all of it, send what you have and we'll ask for the rest.
-
01
The problem you're trying to solve
A sentence is fine. What is going wrong today, or what is missing?
-
02
The people it affects
Customers, internal teams, both? Knowing who uses the software shapes how we scope the work.
-
03
What you've already tried
Prior builds, prototypes, vendors, or decisions you've made. This keeps us from repeating ground.
-
04
Any constraint that can't move
Budget range and timing help us respond usefully on the first pass rather than the third.
Send us the details
Write in your own words. Rough is fine — the notes above just help us reply with something concrete instead of a holding message.
What happens next
We read every message ourselves, so you'll get a reply from a person rather than an automated sequence. That usually lands within a couple of business days, sooner if the week is quiet.
If it looks like a fit, the next step is a short call to understand the problem and answer your questions. We bring the questions; you bring whatever context you have. You don't need slides or a finished brief for that call.
If it doesn't look like a fit, we'll say so plainly and point you somewhere more useful where we can — another approach, another kind of partner, or a smaller scope that makes sense to start with.
Two different starting points
Most first messages come from one of two places. Neither needs a finished specification.
For startups
If you're pre-launch or early, tell us what you're testing and how you'll know it worked. That framing does more for a first reply than a feature list.
We often start with discovery or a scoped first build — neither requires a finished spec, and both are designed to end with something you can show people. It also helps to know who your users are and whether you can reach them right now. If you can't yet, say so; that's useful information, not a problem.
For established companies
If you're modernizing existing software or adding to a platform, context about the current system saves time: the stack, how old it is, and what's painful about changing it.
A short call with your technical lead usually settles more than a long email, and we're happy to do both. We'll ask about procurement early so nobody is surprised later — review cycles, vendor onboarding, security questionnaires. Knowing that timeline up front makes the plan honest.
What we won't do
We won't pass your details to a partner network. We won't add you to a drip sequence. And we won't pretend to be a fit for every project.
If your request is for staff augmentation at scale, or a fixed-price build of something still undefined, we'll tell you directly and suggest an alternative. That answer arrives quickly so you can keep moving.
Before you write
The questions that come up most often before a first project conversation.
Do I need a finished specification to start?
No. A description of the problem in your own words is enough for a first reply. If it's a fit, shaping the work is part of the conversation, not a prerequisite you have to bring. Bring what exists — a rough plan, a prototype, a set of complaints about the current system.
What if I don't know whether we're a good fit?
That's a fine reason to write. Describe what you're weighing and we'll tell you honestly whether we're the right people for it. If we're not, we'll say so and point you somewhere more useful.
How soon should I expect a reply?
Usually within a couple of business days. Messages that describe the problem clearly tend to get a more concrete reply, so specifics help both sides. Messages sent over a weekend wait until Monday.
Will you sign an NDA before we talk?
If your situation needs one, mention it in your first message and we'll sort it out before you share anything sensitive. There's no need to attach documents to the first email.
We're outside the United States — does that work?
Yes. Mention your time zone in the message and we'll propose call times that fit both sides. Our team works out of Boston, and the hours above are Eastern.
Rough description, real reply
If you're already in the message form, you're set. If you'd rather read first, our insights cover the way we approach product strategy, design, and engineering work before a project starts.
thoughtbot works from Boston, Massachusetts, with teams across web, mobile, custom software, AI integration, and UX/UI design.