The work you run by hand, rebuilt as software.

Zetta Metrics builds Ed-Tech platforms and workflow software for institutions that still run on spreadsheets, paper and follow-ups. One already runs an entire abacus program, from the first practice sheet to the fee desk.

What we buildEd-Tech platformsWorkflow automation

2026

Incorporated in Kolkata, India

0

Platforms on one shared foundation

0

Abacus modules running live on MathPath

0

Question patterns behind Krama's mock papers

The shift

From scattered manual work to one system.

Spreadsheets, email threads, chat follow-ups and paper. Every single week.

Xmarks_final_v3 (2).xlsx
NameQ1Q2TotalA. Sen181634R. Das15#REF!—P. Roy171936
ACAccountsNo reply · 3 days

Re: Fwd: Approval needed?

Has anyone signed this off yet? Need it today…

Can you send today's scores?4:12 pm ✓✓
??6:40 pm ✓✓

Worksheet 14

Still to mark: 32 copies

Who has the latest version??

— Mon

Fees, pending

Paid? ✗

Promised Friday

Cash, no receipt

What we automate

If it runs on spreadsheets and reminders, it can run on software.

The same building blocks, applied to whatever your team still does by hand. Pick one to see the before and after.

Assessments and scoring

Before

Paper tests, marking by hand, and marks typed into a spreadsheet.

With Zetta

Timed online assessments, marked automatically and scored on the server.

Approvals and sign-offs

Before

Email threads, and no clear answer to who approved what.

With Zetta

Approval steps by role, with every decision on record.

Content pipelines

Before

Copying between files and checking everything by eye.

With Zetta

Bulk import with automatic structure and quality checks before anything goes live.

Assignments and follow-ups

Before

Chasing people on chat for status and submissions.

With Zetta

Assignments that track every attempt and surface who needs a nudge.

Reporting

Before

Someone rebuilds the same report by hand every week.

With Zetta

Live reports, compared period on period, for anyone allowed to see them.

Fees and payments

Before

Cash in a drawer, paper receipts, and a notebook of who still owes.

With Zetta

Invoices, receipts, online payments and follow-ups, with the day closed out properly.

Access and data

Before

Shared logins and spreadsheets anyone can open or forward.

With Zetta

Access by role, sessions that expire, and controlled exports.

Our position

We don't build dashboards that sit on top of how you work. We build the system you actually run on.

The foundation

Four rules. Every build.

Every product we ship stands on the same engineered foundation, so each one starts further ahead than the last.

Attempt
Payment
Request
Server rules
Scored
Recorded
Routed

The rules live on the server

Scores, timers, approvals and promotions are decided on the server and nowhere else. People see the outcome. Nobody can edit the rule.

MathPath PlatformKrama

Shared foundation

RolesAssignmentsApprovalsScoringReportsAccess

Built once, reused on purpose

Roles, assignments, approvals, scoring and reports are engineered as building blocks, so each new product starts where the last one finished.

audit.log
01attempt.submittedclient
02timer.checkedserver
03scored · server ruleserver
04status → passedlogged

Every decision on record

Who changed what, when and why is logged the moment it happens. Nothing depends on someone remembering.

RoleViewAssignGovern
Admin
Teacher
Student

Every role, its own workspace

Admins, teachers and students each work in a space built for their job, and see exactly what that job needs. Nothing more.

How we build

From manual process to shipped product.

01 · Map

Map the real process

We sit with the people doing the work and map it as it actually runs: every role, every hand-off, every spreadsheet. Then we design.

Request
Spreadsheet
Review
Report
Re-typed by hand
Emailed for sign-off
Checked by eye
Compiled weekly

Every manual step, found before any code is written

02 · Build

Engineer it to last

Roles, rules and records are built as reusable pieces from day one, with security in the first release, not a later one.

Roles
Workflow
Scoring
Access
Reports
Audit trail

Reusable building blocks, engineered once

03 · Ship

Ship it, then keep extending

The product goes live with real users. What we learn shapes the next release, and every new build starts further ahead.

Your system Live
Admin workspace
Team workspace
User workspace
Next module starts ahead, not from zero

Still running a core process on spreadsheets and follow-ups?

Tell us how it works today. We'll tell you plainly whether it's a fit for what we build, and what it would take.