1. Who is the operator?
Legal entity, company number, ownership, trading name, invoicing and contractual responsibility.
Pilot Venture Studio
Controlled entrepreneurial projects with visible responsibility
A practical route for testing a product, service or new organisation under defined support while protecting customers, attributing experience correctly and publishing useful learning.
A pilot is not permission to lower responsibility
Early-stage projects need room to learn, but users, customers and suppliers still need to know who is responsible. Market Accord pilots are designed around a clear legal operator, service boundary, supervision model, acceptance criteria, incident route and decision gate.
The project may use a separate trade name and be run by a third party. That can create a focused identity and give professionals practical experience. It cannot be used to hide ownership, borrow another organisation's history or blur who contracts with the customer.
Pilot control plan
Nine questions before a customer is exposed.
The answers scale to the risk of the service, but none should be silently assumed.
2. What is being tested?
One precise proposition, user group, context, duration and success or stop criteria.
3. What remains untested?
Limitations are stated before participation, not discovered only after failure.
4. Who may be harmed?
Customer, user, employee, volunteer, supplier, community, data subject and market risks.
5. What controls exist?
Competence, supervision, insurance, safeguarding, data, quality, continuity and escalation.
6. What is accepted?
Deliverables, quality thresholds, response times, exclusions and customer responsibilities.
7. What evidence is captured?
Consent, observations, service records, feedback, incidents, costs and improvement decisions.
8. What can be published?
Named, anonymised, aggregated, delayed or non-published treatment is agreed separately.
9. What happens next?
Proceed, change, partner, pause or stop—each with ownership and a review date.
Experience attribution
Evidence must say whose experience it is.
| Evidence type | How it should be described |
|---|---|
| Founder experience | Work performed personally in a stated role, without implying it was delivered by the new entity. |
| Partner experience | Experience belonging to a disclosed partner, subcontractor or associate with its role and availability explained. |
| Organisational evidence | Processes and records created and operated by the current legal organisation. |
| Pilot evidence | Results observed under the precise pilot scope, supervision, limitations and date. |
| Future capability | A plan or commitment clearly labelled as not yet demonstrated. |
No synthetic independence: a project should not be presented as unrelated to Bid Champions or another operator where control, funding, staff, systems or commercial interests are connected. Transparency creates legitimacy; obscurity destroys it.
Propose a controlled pilot.
Explain the product or service, intended user, legal operator, relevant experience, risks and what the pilot must learn. Market Accord will assess fit before any public listing.