From registry services to trusted business infrastructure

KVK Aruba
Growth Roadmap

Lower operating pressure. Stronger data value. More stable revenue. Better institutional relevance.

KVK Aruba already holds one of the most important positions in the island's business ecosystem: the official source of business and organization information. The next step is not simply to build a larger portal, but to create more value from the trust, data and services KVK already owns.

View the opportunitySee phased approach
Trusted Business Data Layer
Banks
Government
Notaries
Entrepreneurs
Non-profits
Accountants

The current reality

High institutional use, limited value capture

High-value users rely on trusted data for serious operational and compliance work, but current access pricing does not yet reflect the value, cost and responsibility behind that service.

Occasional users

Afl. 5 / request

Low frequency · Accessible service

  • Entrepreneur
  • Business owner
  • Small company
  • Foundation / NGO

Small, per-request payments

Professional / institutional

Afl. 100 / year - full access

Repeated use · High dependency · Full data value

  • Bank / compliance
  • Notary
  • Accountant
  • Insurer
  • Government department
  • Legal office
Used for
KYCOnboardingVerificationComplianceRisk review

High-value use · Low-value access price

Trusted business dataOfficial information · Operational responsibility
Revenue in
Value & cost out
Value mismatch

Cost to serve

Hosting
Security
Support
Data maintenance
Document generation
Compliance
Continuity

The pricing model should distinguish between occasional public use and recurring professional value.

Occasional access can remain affordable. Recurring professional and institutional access should be priced as a service.

The opportunity

From basic documents to higher-value services

Keep the entry service accessible, while creating additional document and service layers for users who need more certainty, speed and control.

Today

Limited offer

Basic digital extract

Per request

Afl. 5

Basic database access

Yearly

Afl. 100

No verified tier

No subscriptions

No institutional services

No monitoring / API

Value shift

Tomorrow

Layered service model

Basic digital extract

Afl. 5

Verified extract

Afl. 15

Premium validated extract

Afl. 25

Multilingual / international

Afl. 30–40

Compliance package

Afl. 50–100

Professional subscriptions

Recurring

Institutional data services

Recurring

Monitoring & alerts

Usage

Transaction value

LowHigher per request

Revenue mix

Mostly yearlyOccasional + recurring

Service depth

Single productTiered + institutional

Revenue stability

Limited recurringStronger recurring base

Revenue model

From occasional requests to recurring service revenue

Keep occasional access affordable, while turning ongoing data use into monthly service tiers based on depth, frequency, control and institutional value.

Illustrative revenue logic - examples, not final pricing
01

Occasional access

Public · Small businesses

Simple, occasional information needs - pay only when you need it.

Afl. 5 / requestper request
Low price · High volume · Per request
02

Basic monthly access

Recurring light users

Simple company information with limited recurring access - name, registration, legal form, status, basic address.

Afl. 25 – 50 / monthlimited search volume
Entry subscription · Recurring
03

Professional access

Accountants · Advisors · Legal · Notaries

Detailed company profiles, higher search volume, basic document history, saved searches, monthly invoice.

Afl. 100 / monthper professional user
Recurring · Sticky relationships
04

Professional Plus / Data services

Operational B2B clients

Richer data, bulk checks, validation, file comparison, monitoring, downloadable reports, multi-user access, basic audit trail.

Afl. 250 – 500 / monthscales with depth and volume
Higher value · B2B · Recurring
05

Institutional access

Banks · Insurers · Government · Compliance

Controlled access, role-based users, audit logs, compliance reporting, monitoring, institutional dashboards, API-ready access.

Afl. 750 – 2,500 / monthor tailored annual agreements
Highest value · Strategic · Recurring

Occasional access remains simple and affordable. Ongoing access becomes a monthly service, priced according to the depth of data, frequency of use, level of control and institutional value.

Aruba-scale scenarios

Three illustrative revenue paths

Illustrative ranges only. Final pricing and adoption should be validated through current transaction volumes, user groups, professional demand and institutional interest.

Pilot model
Afl. 75K – 110K / year
  • 200 occasional req/mo × Afl. 5 → Afl. 12,000
  • 20 basic monthly × Afl. 35 → Afl. 8,400
  • 20 professional × Afl. 100 → Afl. 24,000
  • 5 Professional Plus × Afl. 350 → Afl. 21,000
  • 2 institutional × Afl. 1,000 → Afl. 24,000
Approx. total
≈ Afl. 89,400 / year
Growth model
Afl. 175K – 250K / year
  • 350 occasional req/mo × Afl. 5 → Afl. 21,000
  • 40 basic monthly × Afl. 40 → Afl. 19,200
  • 35 professional × Afl. 100 → Afl. 42,000
  • 10 Professional Plus × Afl. 400 → Afl. 48,000
  • 4 institutional × Afl. 1,500 → Afl. 72,000
Approx. total
≈ Afl. 202,200 / year
Mature model
Afl. 350K+ / year
  • 500 occasional req/mo × Afl. 5 → Afl. 30,000
  • 75 basic monthly × Afl. 40 → Afl. 36,000
  • 60 professional × Afl. 100 → Afl. 72,000
  • 18 Professional Plus × Afl. 500 → Afl. 108,000
  • 6 institutional × Afl. 1,750 → Afl. 126,000
Approx. total
≈ Afl. 372,000 / year
Higher value per request
Stronger monthly recurring revenue
Better revenue mix
More value from the same trusted data

Cost & hosting

Cost control starts with infrastructure clarity

Before any hosting decision is made, the current cost base, legal requirements, security needs, data residency, support model and continuity risks should be reviewed objectively.

Current situation

Existing hosting setup

Known operation
Recurring cost pressure
Cost transparency to review
Vendor dependency to review
Assessment lens

Six review criteria

Cost baseline

Annual hosting, licensing, backup, support

Legal requirements

Privacy law, processing, contractual safeguards

Security needs

Access control, encryption, monitoring, response

Data residency

Where data is stored, processed and accessed

Continuity

Uptime, backup, disaster recovery, recovery time

Vendor dependency

Exit options, portability, support dependency

Hosting options
01

Keep, optimize or renegotiate

Current model review

The existing setup may still be suitable, but only if cost, support, security, continuity and dependency are transparent and acceptable.

02

Cloud model

Scalable, but requires governance

A cloud model can offer flexibility and modern security options, but only works well with cost control, access governance and clear operational ownership.

03

Regional hosting model

More local control, if requirements fit

A regional option may improve control, sovereignty and local alignment, but must be tested against uptime, security, backup, support and compliance requirements.

Decision output

Best-fit hosting model

Selected on the basis of cost, compliance, risk, performance and long-term control - assessed against applicable Aruban law, contractual obligations, privacy requirements, data sensitivity, security standards and operational continuity.

Proposed first action

Hosting Cost, Risk & Compliance Assessment

A focused review of the current hosting setup, recurring costs, legal requirements, security needs, data residency, vendor dependency and continuity risks before any larger digital investment is made.

Only after the legal, technical, financial and operational requirements are clear, a responsible hosting decision can be made.

  • Current annual cost
  • Hosting and licensing structure
  • Support model
  • Security requirements
  • Privacy and legal requirements
  • Data residency
  • Backup and disaster recovery
  • Vendor dependency
  • Migration risk
  • Potential savings

Data completeness

A stronger registry starts with richer organization profiles

The registry becomes more valuable when every organization type has a complete, current and verified profile with the right level of information for its purpose, risk and role in the ecosystem.

Verified Organization Profile

Baseline for every organization

Verified organization profile

Every organization profile should include the same verified baseline. Hover or tap a persona to see the enhanced data and the value it creates.

Organization nameRegistration numberLegal formStatusRegistered addressAuthorized representativesContact detailsDocument historyLast update date

Tap a persona →

Layer 01

Basic identity

Name, legal form, registration number, status, address, representatives.

Layer 02

Governance & trust

Board, signatories, documents, reporting status, profile completeness.

Layer 03

Ecosystem value

Subsidies, sector role, banking use, compliance, policy insight and public trust.

Future service model

A clearer service model for different users

Different users do not need the same portal experience. The value increases when services are structured around user needs, access rights, urgency and risk level.

Entrepreneurs

Register, amend, pay, request documents, track status.

Professional users

Accountants, notaries and advisors accessing verified information faster.

Institutional users

Banks, insurers and government using controlled data access and audit trails.

Management

Dashboards on usage, revenue, data quality, service performance and operational bottlenecks.

Service intelligence

Smarter service starts with one connected support layer

A stronger service model should not only improve documents, data access and subscriptions. It should also make daily service easier for clients and staff. By adding a digital assistant inside the portal and connecting communication channels into one service layer, users can get faster answers, submit better requests and follow their case or document journey more clearly. This reduces repetitive questions, improves response consistency and gives the organization better visibility over what clients need most.

Incoming channels

  • Website portal
  • Email
  • Phone request
  • Appointment
  • WhatsApp or chat
  • Document request
  • Client question

Smart Service Assistant

Guidance, answers, intake, routing and status support

Better outcomes

  • Faster client answers
  • Better request intake
  • Fewer repetitive questions
  • Clearer document status
  • Better routing to staff
  • Service insights for management
  • End-to-end communication history

Digital assistant in the portal

Guides users through common questions, document needs, registration steps, payment support and status updates.

Connected communication channels

Brings portal messages, email, chat, appointments and service requests into one clearer service flow.

Service intelligence for management

Shows recurring questions, bottlenecks, response pressure, request types and opportunities to improve the service model.

A digital assistant can become the first service layer for routine guidance, intake and status questions. Combined with consolidated communication channels, it reduces manual pressure, improves consistency and creates better visibility into client demand. Over time, this turns customer service from a reactive support function into a source of operational intelligence.

Phased roadmap

A phased roadmap that starts small and builds value

The first phase should create value without heavy development. Larger technical investments should only follow after the revenue model, cost base and institutional demand are validated.

Start small
Validate
Scale

Phase 1

1–3 months

Value packaging

Product naming, pricing tiers, verified document options, institutional landing page, quick UX improvements.

Phase 2

1–2 months

Cost assessment

Hosting review, infrastructure comparison, vendor dependency, security, data residency and savings potential.

Phase 3

3–6 months

Data quality

Entity coverage, outdated records, non-profit/organization registration, data standardization and completeness.

Phase 4

3–6 months

Institutional access

Bank, notary and government pilot, audit logs, role-based access, professional subscriptions.

Phase 5

6–12 months

Data services

Verification API, monitoring alerts, data services, partner onboarding and recurring usage model.

What success looks like

Success should be measured in operational and financial outcomes

Revenue

  • Higher value per document
  • More subscription revenue
  • Institutional service income
  • API/data service potential

Cost

  • Lower hosting pressure
  • Less manual handling
  • Reduced support burden
  • Clearer vendor control

Data

  • More complete records
  • Higher data quality
  • Better validation
  • Fewer outdated profiles

Service

  • Faster user journeys
  • Clearer access rights
  • Better document trust
  • Improved stakeholder experience

Governance

  • Audit trails
  • Role-based access
  • Management dashboards
  • Compliance-ready reporting

Relevant experience

Proven experience in turning data into operational & commercial value

A track record in connecting business models, trusted data, compliance, AI and operating model design into practical services with measurable impact - across BMW Financial Services, Cargill, intelligence platforms and regulated environments.

10+

Years advisory

13+

Markets delivered

€23M

Annual revenue impact

Production AI

In regulated environments

BMW Financial Services · Cargill · Intelligence platforms · Trusted & regulated environments. See why this background fits the KVK Aruba opportunity.

View proven experience

Recommended next step

Start with a focused discovery sprint

Validate the value model, cost base and first implementation opportunities before committing to larger development.

01

Executive alignment session

Confirm priorities, constraints, decision criteria and internal appetite.

02

Value and cost assessment

Review products, pricing, hosting, data quality, users, institutional demand and quick wins.

03

Roadmap and investment decision

Deliver a phased roadmap with effort, cost, revenue opportunities, risks and recommended sequence.

Direct line

Ready to start the discovery sprint?

Reach out directly — no forms, no gatekeepers. A short call is enough to scope the sprint.

AL

Ashton Lopez

Founder · Qwihi

ashton@qwihi.com+31 6 15 22 54 15