Banking and financial-services event owners
Planning fintech demonstrations inside a banking conference
Fintech companies want to show their products to banks, and your delegates want to see them, but your programme still has to stay balanced.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Decide what a demonstration is for, choose a format that suits the room, and agree selection and content review rules before any company is invited. Treat each demonstration as a content item that needs the host institution's or conference body's review, and as an operations item needing space, power, network and a time slot.
Organisers coordinate. Statements about products, performance or regulatory standing are for the companies and the reviewing institutions to confirm.
What the demonstration is for
A demonstration can educate delegates on a technology, show a partnership between a bank and a fintech, or give new companies a platform. Each purpose leads to a different format and a different selection process.
If the conference is hosted by an association or bank, ask who may endorse companies, since an on-stage demonstration can read as an endorsement.
Format options and trade-offs
| Format | Suits | Watch for |
|---|---|---|
| Stage demonstration (5 to 10 minutes) | Showing a few products to a full room. | Live connectivity, strict time limits, pitch language. |
| Demo zone or booths | Delegates who want hands-on time. | Space, power, network, noise, who staffs it. |
| Panel with embedded demonstrations | A theme such as payments or onboarding. | Balance between speakers, a moderator who holds time. |
| Pre-recorded demonstration | Reducing technical risk. | Review time for the recording, accessibility of the video. |
| Closed pilot showcase | A small group of bank participants. | Confidentiality arrangements, who may attend. |
Selection and fairness
Agree selection criteria in writing before inviting anyone: relevance to the theme, fit with the audience, and a content review pass. Avoid giving a single company the most prominent slot without a stated reason.
Decide whether companies pay a fee, and whether the host or committee approves the list. Record each decision.
Steps to plan the demonstration programme
- Write the purpose and chosen format into the brief, and have the committee approve it.
- Publish selection criteria and a submission deadline to interested companies.
- Ask each shortlisted company for a short description, a demo script and the claims it will make.
- Send descriptions and scripts to the reviewing party, and hold slots until approval is on file.
- Schedule a technical rehearsal for each company, covering power, network, display, backup plan and handover time.
- Log decisions in a decision log and brief the moderator on timekeeping and tone.
Questions for the reviewing institution
- Which statements about products, performance or approvals need your review?
- May a demonstration use real or dummy data? Who confirms it is safe to show?
- Are there rules on promotional language, comparisons or endorsements?
- What may be recorded, photographed or shared after the session?
- If a company withdraws or changes content late, what is the fallback?
Worked example · Fictional example
A fictional demo zone at a banking forum
Fictional organisation and figures, for illustration only.
A fictional banking association plans a conference for 350 delegates and a demo zone with six fintech companies. The committee wants a balanced mix of payments, onboarding and data tools.
The secretary publishes criteria and a submission deadline, receives 14 applications, and the committee shortlists six. The host bank's reviewer needs each company's script and claims a fortnight before the event.
Two companies change their scripts at the last minute. The reviewer has not seen the new versions, so the organiser shows the approved versions only. A technical rehearsal the day before finds a network issue in the demo zone, which the venue fixes.
Use this yourself
Fintech demonstration planning table
Copy this table, add one row per company, and update it as approvals and rehearsals are confirmed.
| Company | Format and slot | Script and claims received (date) | Reviewer and approval (date) | Technical needs | Rehearsal date | Backup if it fails |
|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- Two or three demonstrations, a stage slot each, and a simple review route.
- The venue's technical team has run similar sessions.
- The host institution has a clear process for reviewing company content.
Outside planning help earns its fee when
- A demo zone with many companies, each with different power, network and staffing needs.
- Selection is politically sensitive and needs a neutral process.
- Content review, technical rehearsal and run order must be coordinated across several parties.
Need the demonstration programme coordinated?
A conference project lead can run the selection process, collect scripts and route them to the reviewing party, schedule technical rehearsals with the venue and AV supplier, and keep run order and timekeeping on track. Technical production and statements about products stay with the companies and their reviewers. Send your theme and the number of demonstrations you have in mind.
Questions organisers ask
Should fintech companies pay to demonstrate?
That is a decision for the host or committee. If fees apply, state them in the selection criteria, and check with your finance team how they are recorded.
How long should a stage demonstration be?
Short slots of five to ten minutes keep the programme balanced. Decide with the committee, and ask the moderator to enforce time.
How do we avoid a demonstration sounding like an endorsement?
Agree neutral introductory wording, avoid comparative language and ask the reviewing party how the session should be framed.
What if the live demo fails?
Ask each company for a backup, such as a recorded walkthrough, and rehearse with the venue's network the day before.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.