LINK MBA Capstone
Capstone Presentation
Capstone pitch

LINK is the Digital Baseplate for growing firms.

A finance-aware operating layer for professional-services SMBs that connects the tools they already use across time, projects, invoicing and finance.

Connect, don't replace Quote-to-cash wedge Dutch beachhead
20-100
Employee ICP

Complex enough to feel the pain, not ready for full ERP migration.

4k
Initial beachhead

Estimated Dutch professional-services firms in the target size band.

link.app / dashboard
LINK dashboard product mockup

Open with the simple thesis: LINK is not another tool in the stack. It is the baseplate underneath the stack that makes existing tools operate as one.

The problem

Growth multiplies the gaps between tools.

Professional-services firms often run time tracking, project delivery, CRM, invoicing and accounting in separate systems. The work gets done, but the operating truth is reconstructed manually.

53%
Integrated-system adoption

Only about this share of firms use integrated ERP, CRM or BI systems.

41.08%
Small-enterprise ERP adoption

Cloud adoption does not automatically create an operating backbone.

22 hrs
Monthly admin burden

SMB owners lose material time to financial administration.

4.5%
Revenue leakage risk

Fragmented quote-to-cash creates missed time, billing delays and exceptions.

The leadership question

Did last month's work actually get billed, paid and reflected accurately in finance? In many firms, answering that question still depends on spreadsheets, follow-ups and manual reconciliation.

Keep this practical. The buyer does not wake up thinking about middleware. They feel billing delays, reconciliation effort, exceptions and lack of confidence in the numbers.

First customer

A tight ICP where workflow pain is visible.

LINK starts with Dutch professional-services SMBs whose commercial engine runs through project work, billable time, invoices and financial reporting.

13.88M
SMEs across seven screened Europe-first countries
1.60M
Dutch SMEs in the first national market
263k
Dutch professional-services SMBs
4k
20-100 employee beachhead firms

Workflow

CRM, project delivery, time capture, invoicing, collections, reporting and finance spread across multiple tools.

Pain

Billing delays, reconciliation effort, weak visibility and unclear exception ownership.

Trigger

Operational complexity has outgrown manual coordination, but full platform replacement still feels too disruptive.

The market story should sound disciplined: LINK is not claiming every SME on day one. It starts with a countable beachhead and a workflow customers can understand.

Why the Netherlands, why now

Digital maturity is high, but operational coherence is still missing.

Cloud is not integration

Dutch firms are strong cloud adopters, but the operating layer across tools remains fragmented for many SMBs.

Compliance raises the stakes

Wet DBA enforcement and e-invoicing readiness increase the need for reliable time, contractor, billing and finance data.

EU expansion corridor

The Netherlands is a focused entry point with a practical path into Belgium, Benelux and wider EU professional-services markets.

Avoid overclaiming regulation as a single deadline. The point is direction and urgency: more structured operational and financial data is becoming more valuable.

The solution

Connect, don't replace.

LINK sits between the tools a firm already runs, resolves fragmented records into one canonical model, applies finance-aware workflow logic and writes clean outputs back.

LINK Baseplate
Time tracking
Project delivery
Invoicing
Accounting
CRM

Explain the baseplate metaphor: customers keep their blocks, but LINK gives them the foundation those blocks can snap into.

Product evidence

The concept is already translated into product screens.

link.app / operations
Unified operations dashboard

Operate

Unified dashboard, quote-to-cash reconciliation, profitability and cash visibility.

Configure

Connector health, connection maps, field mapping and no-code workflow rules.

Quote-to-cash screen
Connection map screen
Workflow builder screen

This slide proves that the team has moved past abstract strategy. It shows a coherent product language and the screens needed for the first wedge.

Initial wedge

Close the loop from time logged to cash collected.

1. Log time

Consultants keep using the time-tracking tool they know.

2. Validate

LINK maps time to project, rate and contract.

3. Draft invoice

Compliant drafts are assembled without spreadsheet handoff.

4. Issue

Invoices post to accounting and follow the schedule.

5. Reconcile

Payment status flows back into the operating dashboard.

link.app / quote-to-cash
Quote-to-cash product mockup

The first workflow matters because it is financially consequential. It is where fragmentation turns into delayed billing, missed time and weaker cash control.

Platform architecture

A coordinating layer, not another system of record.

Connector layer

API and webhook connectors for customer tools.

Orchestration engine

Mapping, transformation, rules and reconciliation.

Unified data model

Clients, projects, time, invoices, payments and contractors.

Workflow layer

Dashboards, KPIs, alerts, automations and future agents.

Foundations

EU-hosted RBAC Encryption Audit logs Connector health Peppol-ready outputs

Customer tools remain the systems of record. LINK gives them a shared operating model and a cleaner foundation for later automation.

This slide is for credibility. The architecture is modular enough to start narrow, but extensible enough for adjacent workflows and later AI.

Competitive position

LINK occupies the gap existing categories leave open.

Workflow ownership
Low disruption
Work-management tools
Automation tools
PSA / ERP platforms

More specific

Finance-aware workflow ownership, not generic task coordination.

Less disruptive

Connects existing tools instead of demanding immediate platform replacement.

More repeatable

Productizes implementation learning instead of rebuilding bespoke integration work each time.

More scalable

Creates the structured data foundation needed for automation and agents.

The strongest line: LINK is not trying to be a better Asana, Zapier or ERP. It is solving the gap between them.

Business model

Start service-led. Productize what repeats.

Year 1 model

Assessment Implementation Dashboard Core connectors Founder-led sales

Early revenue blends implementation and advisory work with recurring platform subscription. This keeps customer success high while the product learns.

Scaling logic

Reusable templates Self-service config Lower service hours Subscription tiers Agent-assisted ops

Every implementation should create connector knowledge, workflow rules and playbooks that make the next implementation faster.

Defend the hybrid model as a deliberate wedge strategy. SMBs need help implementing this, and the service layer teaches the product what to automate.

Go-to-market and roadmap

A disciplined path from first cohort to product-led platform.

Year 1

Validate

MVP, selected integrations and concierge onboarding for Dutch professional-services design partners.

Year 2

Expand

Broader workflow coverage, reporting and hardened connector reliability.

Year 3

Automate

Reusable logic, self-service configuration and automations that reduce service effort.

Year 4

Package

Subscription tiers and industry-specific workflows beyond the consulting wedge.

Year 5

Scale

Product-led operating layer across adjacent industries and European markets.

This is where the capstone story becomes credible: narrow wedge, measurable pilot outcomes, then repeatability and automation.

Founding team

Strategy, customer success, market access and platform architecture.

SB

Sachin Bijadi

Concept & Strategy

Digital product and transformation perspective; original concept and strategic direction.

SL

Simeon Labuschagne

Customer Success

Client success, sales, operations and adoption lens for early delivery quality.

WS

Wouter Stegenga

Market & Operations

Dutch operations and procurement consultancy experience; local SMB proximity.

TP

Thiago M. Pinto

Platform Architecture

Data platforms, MLOps and integration infrastructure; technical foundation.

Position the team as balanced. This is not only a technical project or only a consulting concept; the founding roles map to the operating model.

Next step

Validate the wedge with the first cohort.

LINK's immediate goal is to prove measurable value in Dutch professional-services SMBs before scaling the product surface.

Find design partners

Identify firms in the 20-100 employee range with visible quote-to-cash pain.

Run discovery

Map billing delays, reconciliation effort, exception ownership and tool stacks.

Validate willingness to pay

Test subscription plus implementation economics against avoided admin burden.

Convert learning

Turn pilot results into reusable playbooks, workflow templates and roadmap priorities.

LINK is what a growing firm reaches for when the tools it has stop working together, and what stays with it as the foundation everything else is built on.

Close with the baseplate line. The ask is not generic funding language; for the capstone, the strongest next step is market validation through design partners.

1 / 12 00:00