Schedule a meeting

Forty-five minutes with a senior engineer, about your problem.

Pick a time below and it goes straight into a real calendar. There is no qualification call before the real call, no deck, and no obligation at the end of it. If we are the wrong firm for what you are doing, that will be obvious to both of us within the hour and we will say so.

  • 45 minLong enough to get into the detail, short enough to book this week.
  • EngineerYou speak to someone who would work on it, from the first conversation.
  • No deckWe ask about your problem rather than presenting our credentials.

Pick a time

Times are shown in your own timezone. Booking confirms immediately and you will get a calendar invitation with a video link.

Open in a new tab

Loading the calendar. Book in a new tab instead if it does not appear.

Prefer not to use the scheduler? Email hello@brilliantsystems.io or call +1 720 760 9693 and we will arrange a time by hand.

The call itself

What it is, and what it is not.

Booking time with a software firm usually means sitting through a company overview before anyone asks what you need. This is the opposite arrangement, and stating it plainly seems fairer than letting you find out.

What it is

  • A working conversation about your problem, its constraints and what has already been tried
  • An honest read on difficulty, rough cost and how long it would realistically take
  • A chance to ask hard questions about how we work, who would build it and what happens if it goes wrong
  • Useful to you whether or not you ever hire us

What it is not

  • A discovery call to decide whether you are worth a second call
  • A slide deck about our history, values and logo wall
  • A pitch that ends with pressure to sign before a quarter closes
  • The start of an email sequence you have to unsubscribe from

Getting the most from it

Nothing is required.

But if any of these exist, having them to hand turns a good conversation into a specific one. If none of them do, the call is still worth booking.

  • The problem in one sentence

    What has to be true afterwards that is not true now. This matters more than the feature list.

  • What already exists

    Systems, spreadsheets, vendors, the thing somebody built in 2019 that everybody depends on.

  • The date that matters

    A regulatory deadline, a contract, a season. Real dates change the design, arbitrary ones do not.

  • Any quote you already have

    Bring it and we will give you a like-for-like comparison rather than a number you cannot check against anything.

Rather not book

Write instead.

Plenty of people would rather set out the problem in writing and get a considered reply than talk it through cold. That works just as well, and you will still hear back within one business day.

Before you book

Questions people ask first.

Who will I actually be speaking to?

A senior engineer, and depending on the subject the person who would lead the work. Not an account manager reading from a qualification script, and not somebody who has to check with the technical team and come back to you.

Do I need to prepare anything?

No. Come with the problem as you currently understand it, including the parts that are unclear. If you have architecture notes, a previous quote or an internal estimate, they help, but nothing is required.

Is this a sales call?

It is a conversation about your problem. If it becomes clear we are not the right firm, we will say so on the call and point you somewhere better where we can. Nobody will follow up with a sequence afterwards.

What if none of the times work?

Send an email instead and we will find a slot outside the published hours, including early or late to meet a timezone. The calendar shows the usual working window, not the limit of what is possible.

Can other people from my team join?

Please bring them. The most useful calls have the person who knows the constraints in the room, whether that is an engineer, an operations lead or whoever owns the budget.

Where to go next

Certified, partnered and awarded