AVILINKR×TP AEROSPACE
01 / 10
Working session · TP Aerospace
01 / 10
Avilinkr×TP Aerospace

Scope Alignment
Workshop

Agree the scope. Align the rollout.
Define success.

01 · Scope & pricing02 · Implementation plan
Workshop outcomes
02 / 10

Two discussions.
Clear outcomes.

A working discussion — with a scope and implementation plan to confirm afterwards.

01 / COMMERCIAL

Scope & pricing

Confirm what is included, where the shop fits, and which needs require a separate agreement.
02 / DELIVERY

Implementation & success

Align the test group, phased rollout, measures of success and acceptance process.
Christian leads the session. Oliver contributes scope input and coordinates with TP Aerospace.
Discuss

What must we resolve today for TP Aerospace to move forward?

01 · Commercial scope
03 / 10

The scope included
in the subscription.

Commercial Foundation + Bid Governance: one shared workspace for your commercial teams.

Customers & accounts

Customer master, contacts and account teams. Account plans, current offers and next best offers.

Pipeline & daily work

Opportunities and existing sales campaigns. Meeting notes, follow-ups and reminders.

Bid governance

Bid categorisation (1 / 2 / 3), approval workflow, support-trigger logic and response-time tracking.

Reporting & your data

The six dashboards with named KPIs. CSV / PDF export of your own data.
Discuss

Which everyday commercial needs are not covered by these four areas?

01 · Shop and boundaries
04 / 10

One package.
Two connected experiences.

The customer-facing shop is included alongside the commercial workspace — with its operating boundaries to confirm together.

Commercial workspace

Accounts, pipeline, bid governance and reporting for TP Aerospace’s internal teams.

Customer-facing shop

Included in the annual price. Confirm the catalogue, customer access, enquiry / ordering journey and hand-off to the team.
Outside the base scope unless agreed

Advanced Bid Intelligence · Quantum / ERP integration · Inventory Intelligence · AI Intelligence · additional campaign modules.

Existing sales campaigns remain included; additional campaign modules are separately developed capabilities.

Discuss

Which shop workflows and data connections are essential for the first rollout?

01 · Workshop commercial proposal
05 / 10

€10,000 per year.

Updated workshop proposal: existing product scope plus the shop.

During the pilot
€0

Up to 5 hours per month of further development and customisation, at no extra cost during the pilot.

At pilot completion

Paid subscription starts with full rollout.

Proposed for early January 2027, subject to written acceptance of the pilot.

The annual package includes the commercial workspace and the shop.

This proposal is for workshop confirmation. The historical €7,500 offer in the earlier decks is unchanged.

Discuss

Does this package cover the scope TP Aerospace needs to begin?

02 · Proposed implementation plan
06 / 10

Test. Expand.
Then roll out fully.

A staged rollout on real work, refined after today’s discussion.

01 / NOVEMBER 2026

Finish with a test group

Complete and tailor the solution with department representatives. Configure workflows, onboard testers and work through live cases.
Exit check: core workflows ready for wider use.
02 / DECEMBER 2026

Selected-group rollout

Expand to an agreed group. Validate adoption, resolve issues and compare pilot evidence with the baseline.
Exit check: readiness and acceptance reviewed.
03 / EARLY JANUARY 2027

Full rollout & payment

Complete the pilot, obtain written acceptance and open access to the full agreed user group. Paid subscription starts.
Gate: written pilot acceptance.
Discuss

Is this sequencing realistic for your teams, data and availability?

02 · Pilot working model
07 / 10

A small group.
Real commercial work.

One representative from each participating department — testing the solution on their own pipeline.

Nominate & onboard

TP confirms departments and testers. Agree access, required pipeline data and the first live workflows.

Use & observe

Run real opportunities, RFQs and bids. Capture friction, missing needs and the baseline KPI evidence.

Review & refine

Weekly feedback with Oliver and Avilinkr. Prioritise changes within the agreed scope and pilot allowance.

Check before expanding

Confirm core workflows, onboarding readiness and critical issue resolution before adding more users.
Discuss

Who can represent each department, and what could block their participation?

02 · Success criteria for discussion
08 / 10

What would make
this pilot a success?

Agree the measures and targets before testing; review the evidence at pilot completion.

Bid response time

BEFORE TESTINGMedian time from RFQ receipt to first commercial response on comparable cases.

AT PILOT COMPLETIONRepeat the same measure on pilot cases; compare like-for-like.

[RESPONSE-TIME TARGET — agree]

Win/loss completeness

BEFORE TESTINGShare of closed bids with a structured, usable outcome reason.

AT PILOT COMPLETIONReview closed pilot bids for complete, usable reasons.

[COMPLETENESS TARGET — agree]

Time in Excel

BEFORE TESTINGHours per user per week maintaining pipeline and status spreadsheets.

AT PILOT COMPLETIONRepeat the time log for the same users and activities.

[TIME-SAVING TARGET — agree]

Pipeline confidence

BEFORE TESTINGUser confidence survey plus a sample of pipeline records checked against live work.

AT PILOT COMPLETIONRepeat the survey and record checks with the same definitions.

[CONFIDENCE TARGET — agree]

Discuss

Which outcomes matter most, and what improvement would you consider meaningful?

02 · Responsibilities
09 / 10

Who drives the work.
Who confirms it is ready.

Clear delivery roles — and named TP owners for scope, evidence and acceptance.

Avilinkr & coordination

Christian

Commercial lead and workshop facilitator.

Oliver

Internal coordinator between TP Aerospace and Avilinkr; gathers feedback and aligns priorities.

Jarl

Product development, configuration and delivery.
TP Aerospace — nominate

Product owner

Confirms scope and reviews pilot evidence.

Management sponsor

Supports participation and confirms the acceptance authority.

Department testers

Use live workflows and provide feedback and KPI evidence.
Acceptance gate: jointly review agreed KPI evidence and rollout readiness, then obtain written TP sign-off before the paid January rollout.
Workshop close
10 / 10

Agree today.
Confirm the next steps.

Turn today’s discussion into a confirmed scope and a practical implementation plan.

01

Scope & commercial terms

Included functionality, shop boundaries and the €10,000 annual proposal.
02

People & readiness

Participating departments, test users, data dependencies and TP owners.
03

Rollout & success

November–January sequencing, KPI targets and acceptance authority.
04

Written confirmation

Avilinkr updates the scope and high-level implementation plan after the meeting. Both parties confirm before proceeding.

The result: a shared plan — not assumptions.