Tell us about your system

Send a few lines about what you are building or what needs fixing. You will hear back from the architect who would lead the work, with a few questions or a proposed time for a call.

A message from you reaches an architect, then a call Three nodes in a row: you, with a few lines about your system; the contact address, highlighted; and an architect. Arrows lead from left to right, and a last arrow labelled call loops back. You a few lines on your system contact@ basebrainbuild.com read by an architect Architect who leads the work a call, then a scope and a price

Useful to include

  • What the product does, and who uses it
  • What is slow, fragile or missing today, or what you are about to build
  • Your current stack and where it runs, if there is one
  • The load you expect: users, requests, data volume, however you measure it
  • Your timeline, and whether you have a budget range in mind

A short message is fine. We will ask about anything else on the call.

What happens next

  1. A first call We go through your system and your goals, and say openly whether we are the right team for it.
  2. A proposal For well-defined work, a fixed scope and price. For ongoing work, the team, the rates and how we start. For systems that need a closer look first, an Architecture Review.
  3. Kick-off Shared channels, working hours across time zones and an update schedule, agreed before the work begins.

Where we are

Remote-first, working with clients worldwide. We agree shared working hours at the start of each project, so there is always an overlap with your team's day. See how we work for the engagement models and what every project includes.

One address for everything

New projects, reviews, partnerships and questions all go to the same inbox, read by the architects, not a sales team.