Bellcourt Systems

Contact

Talk to the person who would build it

There is no account layer here. Enquiries reach the principal directly, and are answered the same or the next business day.

Send a message

This goes straight to Bellcourt Systems. Expect a reply the same or the next business day.

Fields marked * are required.

What helps in a first message

None of this is required — a one-line note is fine. But if you have it to hand, it lets the first reply be substantive rather than a request for more information.

  • The solicitation number and portalOr a link. We will read the document before replying, including addenda.
  • Dates that cannot moveSubmission deadline, question deadline, and any go-live date driven by something outside the project.
  • What exists todayThe current system, who maintains it, and what specifically is failing.
  • Constraints we should respectRequired integrations, hosting or data-residency rules, accessibility standards, procurement thresholds.

Before there is an RFP

Most software an agency needs never reaches a formal solicitation. It sits below the informal-purchase threshold, or it is a problem nobody has yet written down as a requirement.

Those conversations are welcome and carry no obligation. If you can describe what is going wrong, we can usually say quickly whether it is a build, a configuration, or something you should not spend money on at all.

A note on scope discipline. If a solicitation names a specific commercial product or is shaped around an incumbent system, a custom proposal is normally disqualified on compliance rather than judged on merit. We will tell you when we read a document that way instead of bidding it anyway.