d•ts

Less noise. More control.

A simple employee equipment experience, managed by Dots.

d•ts
Strategy · My proposed approach
02 / 12

One portal. Clear value for everyone.

EMPLOYEE

Easy choice

See approved equipment and track delivery.

IT + HR + FINANCE

Clear control

Set policies once. Handle only exceptions.

DOTS

Managed service

Run the workflow and build recurring revenue.

Policy connects IT, HR, Finance, Procurement, Security and Dots Operations.
Not another online store - one managed process from employee need to delivered equipmentPRODUCT VISION
d•ts
Role · How I would operate
03 / 12

I own the outcome end to end.

CUSTOMERS

Drive adoption

  • Lead discovery and sales
  • Own issues and adoption
DOTS TEAMS

Create alignment

  • Align Engineering and Operations
  • Drive a stable go-live
GROWTH

Make it repeatable

  • Turn feedback into product
  • Build a rollout playbook
I own product and first pilots. Engineering owns the build. Implementation and CS own scaled rollout. Leadership decides major tradeoffs.
First 6 months: prove and productize · first 12 months: standardize and scaleROLE & OWNERSHIP
d•ts
MVP · Employee workflow
04 / 12

Employees choose. Dots handles the rest.

01

Employee joins

Profile and role arrive from HiBob.

02

Secure login

Pre-hire link, then Okta.

03

Choose laptop color

The laptop model follows the job role.

04

Choose peripherals

Bundles or the approved PunchOut catalog.

05

Check policy

Dots checks tokens, stock and approvals.

06

Deliver

Dots orders, ships and updates everyone.

No reimbursement
No IT ticket
One audit trail
One Dots owner
Personal email is a limited preboarding bridge; Okta is the long-term identityMVP EXPERIENCE
d•ts
Solution architecture · How it works
05 / 12

Dots connects the workflow.

COMPANY SYSTEMS

People and access

HiBob, Okta and IT policy.

Dots workflow

One product with flexible rules for each customer.

DELIVERY

Portal and suppliers

Choice, order, delivery and status.

01

Access

Role-based identity and permissions.

02

Policy

Budget, approval, stock and country rules.

03

Fail safely

Pause and notify when data is wrong.

04

Audit

Separate data and keep full history.

If information is missing, Dots pauses safely, explains the issue and sends it to the right ownerSOLUTION & INTEGRATIONS
d•ts
MVP + 12-month roadmap
06 / 12

Start small. Scale what works.

0-90 DAYS

Prove the need

  • Map the manual work
  • Launch 2-3 pilots
  • Test must-have value
MONTHS 3-6

Repeat

  • Simple policy setup
  • Equipment refresh
  • Rollout guide
MONTHS 6-9

Add operations

  • Support workflow
  • Min/max stock alerts
  • More countries
MONTHS 9-12

Expand

  • Employee chat helper
  • Zip, ITSM and ERP
  • Scale through CS
Not in the first pilot: auto-replenishment and advanced integrations.
Future features are earned by customer evidence - they are not part of the first pilot12-MONTH ROADMAP
d•ts
Pilot · How I would execute
07 / 12

Choose the right design partners.

COMPANY

Strong fit

About 2,000 employees, 15 countries and 100 hires per month.

SYSTEMS

Ready to connect

HiBob, Okta and clear IT policies.

PEOPLE

Committed team

An executive sponsor and named IT or HR owners.

The key question: Is this a must-have problem customers will pay to solve?
Dependency owner, date and escalation path are explicit before development beginsPILOT EXECUTION

Run a simple pilot.

01
Discover

Understand today's manual work.

02
Design

Agree on one clear policy and flow.

03
Launch

Onboarding and refresh employees.

04
Learn

Review employee, admin and Dots Ops feedback.

05
Decide

Expand, improve or stop.

Named owners review weekly. New requests go to backlog unless they block the pilot.
d•ts
Value + business model · Illustrative assumptions
09 / 12

Prove customer value.

ADOPTION

Self-service

Do eligible employees complete the task alone?

SPEED

Completion time

How quickly does equipment arrive?

RELIABILITY

Exceptions

Does the workflow finish without failure or support?

SCALE

Customer setup

How fast can Dots launch the next customer?

EXPERIENCE

Satisfaction

Do employees and admins find it useful?

BUSINESS

Commercial proof

Less manual work, faster lifecycle, retention, expansion and willingness to pay.

Build recurring revenue.

Platform subscription

Base fee and fee per covered employee.

MRR and ARR

Predictable recurring platform revenue.

Pre-funded wallet

Quarterly, half-year or annual equipment budget.

Equipment money

Not Dots revenue. Tokens simplify spending.

Setup and operations

Pilot, rollout and special handling.

Service revenue

Dots charges for real implementation work.

d•ts
Learning · Improvement · Decisions
11 / 12

Improve before you scale.

01

Employee use

Signal: people still need help. Action: simplify.

02

Customer setup

Signal: each launch needs code. Action: configure.

03

Reliable data

Signal: missing data. Action: stop and notify.

04

Healthy model

Signal: costs grow. Action: fix the offer.

Customize the rules, not the code.
Mindset: learn early · improve calmly · expand when readyLEARNING & IMPROVEMENT

Earn trust. Bring a clear decision.

01

Access

I need customers, data, a sponsor and committed Engineering/Ops capacity.

02

Lead

I own learning, delivery and stable adoption.

03

Recommend

I state assumptions, test risk and bring clear options.

I own the outcome and execution. Leadership decides how far to invest.