Avilinkr × TP Aerospace — Management Meeting Deck
From commercial fragmentation
to one operating system
Management meeting — introduction, live demo, price, and a concrete path to pilot.
Five blocks, 90 minutes.
The demo gets the most time — that is where the real discussion happens. We keep introductions and price short.
Who we are and how we build — and where the product fits.
The current product, live — and how it fits your commercial process. Questions welcome throughout.
What the subscription costs and what it includes.
From today's version to an aligned system and a running pilot.
Project organisation, roles and the decisions we need today.
Commercial software for the aviation aftermarket, built with operators — not for them.
Digital products, AI-native software, UX & workflow design
Aftermarket, MRO & wheels/brakes, commercial workflows
Strategy, B2B SaaS, scaling & adoption
Why we build it the way we do.
We build from how an RFQ actually travels through your organisation — not from a generic CRM object model.
A working product first, then shaped with the people who use it daily. That is why we show you a live system today, not a slide of one.
Customers, bids, pipeline and history captured as structured data. AI is only useful on top of that — never instead of it.
Quantum stays the transactional backbone. We add the commercial layer that today lives in Excel and inboxes.
The product you are about to see is the result of that method — not a prototype built for this meeting.
The product is live. Let’s open it.
A running instance with demo data — the same build we would align to TP Aerospace.
demo.avilinkr.io
What changes in the commercial working day.
RFQ sits in an inbox until someone picks it up
RFQ is registered, categorised and owned within minutes
Pipeline lives in individual spreadsheets
One shared pipeline, visible per account and per department
Win/loss reasons are anecdotal
Win/loss captured on the bid — usable in the next negotiation
Management asks for a status report
Management opens a dashboard
Hours per week maintaining Excel
The system maintains itself as the work is done
Nothing here requires a new process. It captures the process you already run.
€7,500 per year. Nothing until it is proven.
Up to 5 hours of further development and customisation every month — at no extra cost — so we can tailor the solution to your needs while it is proven on real work.
per year for the Commercial Foundation + Bid Governance. The term starts on written sign-off, not on signature of intent.
If TP Aerospace does not continue after the first 12 months, no further subscription fee applies.
- Customer master, contacts and account teams
- Pipeline / opportunities and sales campaigns
- Meeting notes, follow-ups and reminders
- Account plan, current offer / next best offer
- Bid categorisation (1 / 2 / 3) and approval workflow
- Support-trigger logic and response-time tracking
- The six dashboards with named KPIs
- CSV / PDF export of your own data
Two weeks to align. Then the first users are in.
We agree scope, pilot departments and the people who will test.
Fields, bid categories, approval rules, users and roles configured to how TP actually works. Existing pipeline data for the pilot users loaded.
One person per department onboarded on their own live pipeline — short session, then daily use.
Real RFQs and real bids run through the system. We adjust weekly on what they report.
Once the pilot users work in it without friction, we open access to the wider teams.
One tester per department, on their own pipeline.
Small enough to move fast, broad enough that every part of the commercial organisation is represented.
- One user from each department: [DEPT 1], [DEPT 2], [DEPT 3]
- Each works their own live pipeline — no parallel test data
- Oliver coordinates them on the TP side
- Register and categorise incoming RFQs
- Run bids through the approval flow
- Keep their pipeline and account notes in the system
- Report friction weekly — we adjust the same week
- Pilot users work in it daily without workarounds
- Bid response times are visible and improving
- Their pipeline is trusted enough to report on
- Then: rollout to the wider teams, phase by phase
We do not ask the organisation to change before the product has earned it. One user per department proves it first.
A small group, clear ownership on both sides.
- Christian
Front figure and commercial owner of the partnership
- Jarl
Product and delivery — configuration, build, weekly adjustments
- Oliver
Aviation domain — translates aftermarket reality into the product
- Oliver
Internal anchor — coordinates between Avilinkr and TP Aerospace
- [PRODUCT OWNER]
Owns scope decisions and signs off on delivery
- [MANAGEMENT SPONSOR]
Backs the pilot and clears blockers
- [PILOT USERS]
One per department — daily use and weekly feedback
One weekly 30-minute working session with Oliver and the pilot users during alignment and pilot. A short status to the management sponsor every second week.
What we would like to leave this room with.
Confirm the pilot departments and name one user from each
Name the TP Aerospace product owner and management sponsor
Agree the start date for the 14-day alignment window
Hand over the data we need for the pilot users' pipelines
Book the onboarding session for day 15
Two weeks of alignment, one user per department, and you will know within six weeks whether this is the commercial system TP Aerospace should run on.