Skip to content

In cricket, how you step up to the crease
decides how you end the game.

While professional teams have analysts, archives and tools, the pitches that produce tomorrow's stars keep records in notebooks and WhatsApp threads. CreaseTech gives grassroots cricket a modern home — scheduling, facility management, role-based drills, match score ingestion and data-driven insights — so every session, match and milestone becomes part of a visible, coachable journey.

A cricketer's life in one frame — a crawling baby on backyard grass through seven ages to a young batsman raising his bat to a floodlit stadium.

From first net to first selection.

Every training counted. Every innings kept. Every player seen. Every season proven.

Most of the people on this platform are children. It has been designed accordingly.

See the child-safety commitments
Why we built this

Everything the next generation becomes starts on a school ground.
Almost none of it gets recorded.

On grassroots grounds and in practice nets across the world, young players train, bat, bowl and field, and coaches who know their craft watch closely and judge well. Then the season closes.

The cupboard

The scorebook goes into a cupboard.

A season of innings becomes a physical object nobody opens again. Nothing about it is searchable, comparable or portable.

The hard work

The work nobody wrote down.

Months of early mornings and late evenings, the sweat and the bruises — with no record of the sessions done or the drills worked on. Only a memory, and memories fade.

The handover

A coach moves to another school.

Years of development knowledge leave with them. The next coach begins again from the first delivery — and the coach who did the work is forgotten.

The scroll

The WhatsApp group scrolls past.

Planning, strategies, attendance, fees, fixtures, feedback and photographs all live in a feed that deletes itself by design.

Three seasons of work later, the player has almost nothing to show for it — and the institution cannot prove what it built.

Cricket has never been short of talent. It has been lacking how we nurture them.

None of this is anyone's fault. All of it is fixable.

CreaseTech keeps the record where the work happens — so the season, the sessions and the coaching all outlive the scorebook.

Who we are

CreaseTech exists to keep the evidence — and to turn it into better decisions.

We are building one platform where the operational life of a cricket institution — training catalogues and plans, sessions, fixtures, attendance, fees, communications and performance — lives in a single connected system.

Every session a player attends and every innings they play becomes part of a permanent, verified, portable development record that belongs to them and outlasts any one coach, term or committee.

Cricket-specific, on purpose

Built around overs, innings, spells, sessions, drills and age groups — the vocabulary a Master-in-Charge already uses. Generic sports software makes coaches translate; we don't.

Sri Lanka first, not Sri Lanka later

Designed for the Sri Lankan grassroots game as it actually runs — the school calendar, the inter-school season, local payment habits, local scoring sources, and phones running on mobile data.

The record belongs to the player

Portable across schools, academies and clubs. A player who moves does not start again from zero, and a coach's contribution stays attributed.

Vision & mission

Vision

A game where every young cricketer's effort is seen, kept and carried forward — however far they go.

Talent is not cricket's problem today. Memory is. We want a generation of players whose work is visible wherever they go, and schools, academies and clubs that can prove what they built.

Mission

To make every young cricketer's journey count — not only the ones that end in a cap.

We give players, coaches, parents, and the schools, academies and clubs behind them one place to record every session and every innings, see honestly how the work is developing, and decide what comes next. By joining a player's full development record to the coaching knowledge around it and the real context of each match, we turn scattered effort into evidence — so that whenever someone looks, the work is there to be seen.

  • Replace scattered scorebooks, spreadsheets and chat groups with one connected record
  • Turn what a coach already knows into evidence they can show
  • Protect every child on the platform by design, not by policy
  • Make the record travel with the player, not the institution
What we will never claim

We do not select players, we do not coach, and we will not promise a win, a cap or an improvement percentage. What we promise is that when a selector, a parent or a committee looks — the evidence exists.

The value we strive to offer

The idea at the centre is a loop, not a database.

“Excellence is not a singular act, but a habit. You are what you repeatedly do.”
Will Durant, The Story of Philosophy, 1926, on Aristotle

So we built a loop that carries a young cricketer towards excellence.

Stage 01 of 03

The CreaseTech data loop Coaching data feeds training data, training data feeds performance data, and performance data feeds back into coaching data. COACHING DATA TRAINING DATA PERFORMANCE DATA THE LOOP

Stage 01

What was actually taught

Coaching data records what was taught, to whom, and at which stage of a player's development.

A coach opens the squad and sees the stance work already covered in week six.

Guidance becomes individual instead of repeated.

Hover or tap a node for a live example.

The institution

Institutional memory

A season's record that survives the people who created it — administration, scheduling, billing and reporting in one governed system.

Six seasons · three coaches · one unbroken record

Coach A Coach B Coach C S1S2 S3S4 S5S6

Three coaches, two age groups, one continuous record. Nothing leaves when they do.

The coach

Less admin, more coaching

Squad development visible at a glance, administrative load carried by the system rather than by hand, and the evidence behind the interventions you already know are needed.

  • Attendance and session plans recorded once, reused all term
  • Drill exposure totalled automatically, per player and per squad
  • Reports generated from the record, not retyped into a document

The player

A roadmap you can see

What you are working on, how it is developing, and a record of your own that travels with you between institutions.

The caregiver

Honest visibility

Your child's growth shown plainly, inside a structured and accountable training environment — with you in control of what is shared.

Why this matters beyond one school

Elite cricket gets the resources. The grassroots game that feeds it doesn't.

The early years set a player's trajectory — and almost none of those years are kept. A season ends, and the record leaves with the coach.

CreaseTech keeps it. Every player's training and performance, tracked across seasons, holding the whole player — roles, versatility, progress — in one record rather than five.
It shows where the skill gaps and squad gaps are. And lets training be curated to close them, with new drills and mentoring added as the game evolves.
It gives coaches and administrators the tools and data in one place. So time goes back into strategy, into players, into understanding what's happening in a young cricketer's head.
It gives players their own evidence to work from and to be proud of. It gives parents a clear view of where their child stands, and the footing to guide them through the hard years.

And at the level above, the talent and its history sit in one place — sliceable by age, role, format and conditions, so the next generation of squads is built on evidence.

One unified platform for grassroots cricket — looking beyond today's match.

Where the streams intersect — the analysis that mattersWhere the streams intersect

Plan outcome

Did the term's training objectives actually show up in match returns?

ObjectiveLift strike rate to 110
110 target
ResultStrike rate over 9 innings
118 +8 met
ObjectiveFace 38 balls per dismissal
38 target
ResultBalls faced per dismissal
31 −7 missed
Plan versus outcome — open the season sample record

See all four running on a real season.

A worked example built from one term of school cricket — the objectives set, the sessions delivered and what the scorebook returned.

Platform

Dedicated working modules, one connected system, a novel user experience.

Each module delivers its own value — but together they create a seamless development chain. A session scheduled becomes a session attended, becomes drills completed, becomes a season programme. Training connects to match performance, performance becomes insight, and insight becomes a record that can be shown, shared and built upon.

What it does

Three tiers of capability, one connected system.

Tier 01

Coaching & development

The cricket work — planned, delivered, measured.

Drill & skill catalogue

Structured drills, tagged to the skill being coached.

Session & season plans

Term plans built from the catalogue, reused each season.

Match & performance capture

Innings, spells and dismissals read as a season.

Tier 02

Insights & celebration

What the record gives back.

Training and performance, crossed

Committee reports generated, not reconstructed.

Leaderboards & badges

Consent-gated, age-aware recognition.

One record

The player's season and career record, kept.

Tier 03

Core operations

Onboarding, scheduling, facilities, fees.

Identity & onboarding

Centralised profiles, guardian consents, role tags.

Calendar & facilities

Grounds, nets, coaches and kit in one calendar.

Fees & administration

Invoices, receipts and fee position, always current.

Communications & CRM

One record instead of five chat groups.

The modules in detail
Module cards: identity, profiles and onboarding — one person, one identity and a record that moves with them, with guardian consent captured once across school, academy and club; calendar and resource scheduling — the term scheduled in one afternoon, showing two weeks of net bookings with one clash flagged at the point of booking; and match scores and performance — dismissal patterns across the last six innings, four of which ended caught behind to off spin.
Groups, sessions & fixtures

Marked before the players leave the ground

The operational spine: build squads and age groups, schedule the term, mark attendance in the field on a phone, and capture what happened while it is still fresh.

Player A
Player B
Player C · injured
Player D
Communications & CRM

Out of five chat groups, into one record

Announcements, reminders, receipts and consent requests — sent from the system that holds the facts, with a record of what was sent, to whom, and when.

Squad announcementFee reminder delivered · logged
Training drill catalogue

Every drill tagged, every plan reused — and the term's work made visible

A structured drill and skill catalogue, plans built from it, and a record of what was actually delivered to each player — the coaching data that starts the loop. Below: one term's drill load for an under-15 squad, broken down to the skill being coached.

Share of sessions by skill coached across 100 sessions for an under-15 squad in term two: batting 40 percent, bowling 30 percent, fielding 20 percent, wicket-keeping 10 percent.
Institute administration

Every rupee reconciled, every action auditable

Everything an institution runs behind the cricket: term fees and guardian payments, roles and permissions, seasons and settings — with a double-entry ledger behind every rupee, every refund linked to its payment, and a reason code attached to every action.

One squad's term reconciled: term fee for the under-15 squad plus 24,000 LKR, a refund of 2,000 for one player who withdrew, a ledger balance of 22,000 and a variance against bank of 0.00.
How it fits together

A one big HAPPY family (May be a School, Academy or a Club)

The people who use it, the platform that runs the institution, the record it builds, and the outside services it connects to.

Inside your institution · governed and audited

The people

Five roles, one governed system

PlayerTheir work. Their progress.
CoachPlans training. Reads the squad.
GuardiansConsent. Oversight. Visibility.
AdministratorsOnboards. Coordinates. Supports.
Committees & trusteesFunds it. Asks for the evidence.

The cycle they run

CoachTrainPlayAnalyseImprove

Each role sees only what their permission allows.

1they record the work

The CreaseTech platform

Everything an institution runs

Identity & consentGuardian linking, roles
Calendar & sessionsAttendance and bookings
Drills & training plansCurated to the skill gap
Matches & performanceInnings, spells, fielding
Fees & administrationInvoices and receipts
Messaging & reportingSent from the facts
LeaderboardsConsent-gated, age-aware
AnalyticsRates, not counts

Every action consented and audited.

2it becomes one record

One record

Kept across seasons, owned by the player

It belongs to the player and travels with them.

3 · it only leaves with consent
scores and fees come back in — read only

Third-party sources

Connected, never in control · outside your institution

Match & tournament scoresScorecard repositories
Social mediaConsent-gated share cards
Payment providersFees and settlements
MessagingDelivery and receipts

Data flows out only where consent allows it.

Read it as a sentence: the people record the work, the platform turns it into one record, and that record only leaves the institution through the consent gate. Scores and fee settlements come back the other way — read only, never authoritative.

Nothing about a player under 18 crosses the gate without their guardian's explicit permission, and withdrawal removes public visibility immediately.

Training → performance pipeline

Each module adds value; together they form a continuous development pipeline.

From scheduled session to completed drills, from season plan to match performance, and from data to a shareable record. Click any stage to see the raw data it holds, the metrics derived from it, and what it tells a coach to do next.

Reporting

Reports generated, not reconstructed.

Reproducible from the underlying record, every time. Squad depth, participation, attendance, fee position and development progress — the reports a committee actually asks for.

Squad performance

4 of 12

first-innings leads converted to outright wins

4 converted · 8 not

Player progress

19 of 36

scores past 30 that went on to a fifty — 52.8%

19 converted · 17 did not

Skill gap

22% → 15%

of overs bowled to off spin returned this share of wickets

22% of overs 15% of wickets

Same scale. The gap is the finding.

Discovery, leaderboards and sharing

Once the record exists and consent allows it: discovery of coaches and facilities, age-group leaderboards, and moments a family can share. Minors pseudonymous and opt-in only. Share cards are generated from verified data, never from claims, and nothing leaves your institution without passing all four consent gates.

Squad analytics At launch

Exposure-normalised, so a busy player and a quiet one can be read the same way.

Readiness score

74 / 100

74 8 weeks agonow

Workload

9.4 hrs/week

9.4 8 weeks agonow

Skill progression

+12% this term

+12% 8 weeks agonow

Attendance

91% of sessions

91% 8 weeks agonow

Indicative figures from the sample season. Each card expands to drill-level detail and exports as a PDF snapshot.

Recognition At launch

Leaderboards, badges and streaks

Recognition for work done, not just runs scored. Two safeguards hold throughout: leaderboards are pseudonymous for under-16s, and badges are visible to guardians before they are visible to anyone else.

Drills completed · under-16 · this term

1 Player 0413Under-16 · batting 96
2 Player 0288Under-16 · pace 91
3 Player 0517Under-16 · wrist spin 88
12-week attendance streak 100 drills completed Season milestone

Streaks measure participation. Nothing is published outside the institution without passing all four consent gates.

Scheduling & facilities At launch

The term scheduled in one afternoon, without double-bookings.

Grounds, nets, coaches and equipment in one calendar. Bookings carry through to attendance and billing rather than living in a separate conversation, and clashes surface as you make them.

Term 2 · week 6 Main ground, two nets, four coaches
Static preview
Facility utilisation, this week

68% utilisation · one clash outstanding · roster auto-fill pending guardian consent for two players.

Built for everyone the game depends on

Player

Track progress, get personalised drills, build your own record.

View training plan Submit match feedback Share a highlight

Coach

Plan the term, see what worked, get your time back.

Build a session Mark attendance Read the squad
See the coach view See the coach view

Guardian

See where your child stands, and consent to what is shared.

Approve consent View progress Contact the coach
See the guardian view See the guardian view

Management

Run the season, prove the investment, keep the record.

Onboard a squad Schedule the term Generate a report
See the management view See the management view
In depth, by role

Operational efficiency, season readiness, and a memory that stays within

How is our preparation for the next season? Have we done enough for the next Big Match? Don't sit in the dark — CreaseTech shows you where your team actually stands.

  • Season readiness at a glance — how ready the squad is, and where the depth is still thin
  • Is the investment paying off? Which age groups and skills need more help?
  • One dashboard for the whole story — the work put in, what the squad gained, where they stand
  • A season's record that survives staff changes and committee turnover
  • Child-safety posture you can show a parents' association
  • Administration, scheduling, billing and fee position in one governed system

What changes on day one

The term is scheduled in one place, attendance is marked on a phone at the ground, and the first report the committee asks for is generated instead of reconstructed.

Trust is part of the product

Most of the people on this platform are children.

It has been designed accordingly. Guardian linking and consent controls, age-appropriate access restrictions, permission-based visibility, role-based access, complete audit trails, and data export and erasure rights are enforced by the system itself — rather than promised in a policy document.

Nothing about a young player becomes visible beyond their institution unless the right people have agreed to it.

Request the child-safety brief

Gate 01

Identity verified

The record is attached to a resolved player identity, not a name typed twice.

Gate 02

Guardian consent

A minor's data does not leave the institution without the guardian's explicit permission.

Gate 03

Institution posture

Your school decides whether it publishes at all, and under whose name.

Gate 04

Visibility scope

Who exactly can see it, for how long, and how quickly it can be withdrawn.

Privacy centre

Four promises are only worth the three mechanisms underneath them.

Retention, portability and access — each auditable. Data is stored securely, access is logged, and guardian consent is required for every profile belonging to a minor.

Data retention

A player's record is retained while their institution holds a relationship with them, and travels with the player on request. Consent records are timestamped and kept for the life of the account.

Export & portability

Players and guardians can export the full record. Export requires guardian or admin approval, and every export is logged and time-stamped.

Access control

Role-based permissions with least-privilege defaults. Admins audit permissions and issue temporary access from one console.

Who built it

The Team

Built by people who live and breathe cricket — and who have stood in enough nets, on enough boundary lines and in enough planning meetings to know how the grassroots game actually works.

We went looking for its heartbeat. How a session gets planned on a Tuesday and rebuilt on a Wednesday when half the squad doesn't turn up. How a coach carries a whole season in their head and the gear in the back of the car. How a young player gets picked, moved up the order, dropped, forgotten, found again. What a parent watches from the boundary — and everything they're never told.
So before we wrote a single line of this platform, we modelled grassroots cricket end to end. Every role, every workflow, every hand-off, on the field and off it. Months of research, argument and building later, it's nearly ready to hand over.

Because we believe the kid at the far net deserves what the top of the game gets.

Because how a cricketer is brought up decides what that cricketer becomes.

A new era for the grassroots game, built for the game we grew up in — by people who never really left it.

Co-Founder Priyan Platform Engineer + Data

Priyan Indika

Co-Founder Dharshana Chief Technology Architect

Dharshana Chandrasekara

Founder Janith Founder & Head of Cricket

Tharaka Samarathunga

Founder Rasika Founder & Product Strategist

Rasika Senarath

Co-Founder Lakmal Lead Platform Engineer

Lakmal Wimalarathne

Join the movement

We are looking for the institutions who want to help build this.

Not customers yet — collaborators. Early adopters who would like to join hands and help us roll out the best possible product for the development of grassroots cricket.

What a founding institution gets

  • Founding pricing, grandfathered for the life of the relationship
  • Priority onboarding ahead of the February 2027 launch
  • Direct input into the roadmap while it is still being decided
  • Founding-member recognition once you are live

The institutions who have already walked up to the crease

Your institute could be next

Names published only with each institution's written permission.

What we ask in return

Honest feedback through the build, one committee conversation, and permission — if you are happy — to say you were first.

Who believes in us
Serendib International Cricket Academy

One academy has committed so far. Two more are in conversation, and we will name them here the day they say yes — not before.

Crease It

CreaseTech's newsletter on the game as it happens.

Crease It is where we write about cricket in public. Brief analysis of current cricket affairs and match analysis — the same way we read a scorecard inside the platform, applied to the games everyone is already watching. It is how we build a following, and how you can see how we think before you ever log in.

Current affairs

What is happening in the game right now, read short and read straight — selections, schedules, structures, and what they mean for the players coming through.

Match analysis

One match, a handful of numbers, and the passage that decided it. Exposure-normalised, the way a coach would want it, not a highlights reel.

For the fans first

Free to read, no account needed. If it is useful to a supporter, it is useful to a coach — and that is the audience we are building.