SUPPORT · FOR INSTITUTIONAL TEAMS

BCC supports institutional teams where they need it.

Resources, documentation and direct contact for teams already using BCC Terminal or preparing for deployment. If you're looking for a demo, head back to the homepage — this is the resource hub, not the sales funnel.

START HERE

Six resources institutional teams reach for most often.

API Library

REST endpoints for data-warehouse integration + SSO SAML setup. Enterprise tier.

See contact

Sample DD pack

What a committee-ready DD artefact looks like — one page, redacted.

See example

Frequently asked questions

Pilot, pricing, integrations, dashboards — 9 groups of 3-minute answers.

Browse FAQ

Contact the team

Enterprise enquiries, partnerships, procurement pack. We reply within one business day.

Contact form
DIRECT CONTACT

Institutional support — one business day.

SALES / PILOT
sales@bcc.bg

Demo requests, pilot conversations, references under NDA.

TERMINAL SUPPORT
support@bcc.bg

For current pilot and enterprise clients — tech support, integration, dashboards.

HOURS · SOFIA
09:00-18:00 EET

Monday–Friday. Outside hours — contact form, next business day.

Regional banking/fund leads — on request during the first qualification call. Diana Miteva runs the partnerships channel.

FAQ

Frequently asked questions.

WHO IT'S FOR

  • Who's the primary buyer of BCC Terminal?

    Credit-risk and investment-committee teams inside banks, investment funds, institutional developers and analytical advisory firms. NOT for retail users or single-user profiles.

  • How is bcc.bg different from terminal.bcc.bg?

    bcc.bg is the registry — the public facts about every project and every company. terminal.bcc.bg is the institutional decision surface on top of that registry — with ratings, DD workflow, committee outputs, audit trail.

  • How does index.bcc.bg fit in?

    index.bcc.bg is the public methodology hub — BCC Market Index (market pulse), BCC Company Index (company rating), BCC Company Index · Verified (verified layer). Terminal sits on top of all three and turns them into committee output.

PROCUREMENT + SECURITY

  • Is there a procurement pack?

    Yes — security review, DPA, insurance certificates. Sent at first qualification or to your IT/security team on request.

  • How do users sign in to Terminal?

    SSO SAML (Azure AD / Okta / Google Workspace) on enterprise tier. IP whitelisting on opt-in. Every user session is audit-logged.

  • Does Terminal store customer personal data?

    No. Terminal reads from public company and project registries, plus your own internal artefacts (only via your submission). No personal customer data outside explicit opt-in.

PRICING + PILOT

  • How is pricing structured?

    Enterprise tier — by individual proposal. Scoped by banking book, seat count, integration scope. No public price sheet.

  • Is there a pilot?

    Yes — a 60-day pilot against 3-5 projects from your pipeline. Real committee outputs, no commitment. One committee paper — you decide.

  • When do we get the first committee output?

    5-7 business days from pilot start. Data-warehouse integration — 2-4 weeks.