Skip to main content
RoundDigital
Submit an RFP

The nine answers that end a procurement review.

Every enterprise and public buyer runs the same due-diligence list before a contract is signed. Publishing our answers — including the ones still blank — removes weeks from that review and tells you exactly what risk you would be taking.

Four of these say “not yet written”. That is deliberate. A supplier who tells you where their documentation stops is easier to evaluate than one who lets you find out in week three — and the blanks here double as our own funding list, in priority order.
1Published

Published and answerable today

4Drafted

Drafted, awaiting written confirmation

4Not yet written

Not yet written — and named as such

The due-diligence list

Who exactly are we contracting with?Published

Round Digital, successor to Pragra LLC, trading since 2017 and headquartered in Mississauga, Ontario. The corporate chain from Pragra to Round Digital is documented, and the entity position for each jurisdiction is published rather than kept in a sales deck.

Evidence: the capability statement, and the jurisdiction page.

Insurance, limits and certificatesNot yet written

Not yet published. Commercial general liability, professional indemnity, and cyber liability — with named limits, the carrier, and the ability to name an additional insured. Nearly every enterprise master agreement and public solicitation asks for these before anything else, and we cannot answer today.

Highest-value gap on this page. A certificate of insurance is the cheapest procurement unlock we have.

Security posture and controlsDrafted

No independent audit is held, and we will not imply one. What we can publish is the control set actually in force — access management, encryption in transit and at rest, endpoint posture, logging and retention, and how a client environment is separated from ours. [CONFIRM: control inventory and named owner]

Interim: publish the control set as a self-assessment, labelled unaudited, with the roadmap linked beside it.

Data protection, processing terms and sub-processorsNot yet written

Not yet published. A standard data processing agreement, a named sub-processor register, and a stated position on cross-border transfer between the Ontario and Noida centres. For any European engagement this is the first document requested; for Canadian public work the residency question follows immediately.

Prerequisite. Its absence blocks any United Kingdom or European Union pursuit outright.

Past performance an evaluator can actually callDrafted

Three references are published, each with the challenge, the approach, the outcome and the period of performance. Two are related entities, which we state rather than obscure. What is missing is a public-sector reference and any contract value.

One municipal or provincial engagement, at any size, changes the shape of every bid that follows it.

Capacity, key personnel and surgeDrafted

Twenty-plus people across two delivery centres. What a solicitation actually scores is named key personnel with role, tenure and screening status, the bench depth behind each role, and how we surge. [CONFIRM: key personnel list and CV pack]

Required. Most solicitations score key-personnel CVs directly.

Business continuity and disaster recoveryNot yet written

Not yet published. Recovery time and recovery point objectives, the failover position between Ontario and Noida, tested restore evidence, and what happens to a client engagement if one centre is unavailable.

Commonly scored. It appears in most enterprise master agreements and public evaluations.

Escalation path and service levelsDrafted

A named engagement lead, a documented escalation ladder with response targets by severity, and the executive who owns the relationship. Our two-timezone footprint is a genuine advantage here and is currently unstated. [CONFIRM: severity matrix and response targets]

Quick win. Drafting this costs days, not months.

Transition-out and exit planNot yet written

Not yet published. What the client owns, how source, credentials, data and documentation are handed back, the knowledge-transfer period, and the wind-down schedule. This is the most under-answered question in the market — and it is the exact promise this company already makes: systems your team can still run after we leave.

Strategic. The brand promise is unbacked until this document exists.

Credentials are tracked separately, with dates, dependencies and indicative cost, on the certification roadmap.

Four ways in

Only one of them is a solicitation.

An RFP is the last step of a buying process, not the first. These are the three steps before it, each with a stated response time and nothing attached.

01No contact required

Read the capability statement

Entity and registration detail, past performance, delivery footprint and the credential roadmap — in the format an evaluator already files.

Immediate · no form

Everything needed to decide whether to shortlist us. No gate, no email capture, no follow-up sequence — gating this document would contradict the entire premise of publishing our gaps.

We need nothing from you.

02Twenty minutes

Book a qualification call

A direct conversation about whether we are a credible bidder for the specific thing you are buying.

Booked within 2 business days

Twenty minutes with someone who can answer contracting questions — not a discovery call in disguise. If we are not the right supplier for your requirement, we say so on the call and tell you what kind of firm is.

We need: the requirement in one paragraph, and your timeline.

03One upload

Send us your vendor questionnaire

Send your standard supplier or security questionnaire and we return it completed, with every unanswerable item marked rather than left blank.

Returned in 5 business days

Most suppliers stall here for weeks. We return the document with each item answered from our published posture and every gap marked explicitly — so your risk team can score us honestly instead of chasing us.

We need: your questionnaire, and the deadline it has to meet.

04Full solicitation

Submit an RFP or statement of work

A solicitation, statement of work, or staffing requirement. We respond with a go or a no-go, and the reason.

Go / no-go within 3 business days

We tell you within three business days whether we intend to bid, and if not, why — a credential we do not hold, a jurisdiction we cannot contract in, or a capability we would have to subcontract. A fast no is worth more to you than a slow maybe.

We need: the solicitation documents and the submission deadline.

Send us the list your risk team actually uses.

If your questionnaire asks something this page does not answer, that is useful to us. We will complete it, mark what we cannot answer, and add the gap to the list above.