Fitenta
Paper in · Records out
Step 1
Capture
Get the page off the desk and into the system
The bottleneck · what we build
Step 2
Extract
Read the handwriting into fields
Largely solved · composed
Step 3
Use
Records, coverage, exports, reporting
Standard software
What it looks like

Two views of the same page.

The teacher stays on WhatsApp. The school gets a record it can act on. Nothing new to install on either side.

Two WhatsApp conversations with Fitenta: a teacher sends a photo of an enrolment register and of a lesson plan, and Fitenta replies with what it read and what it needs to check
Teachers' WhatsApp viewSend a photo · answer a question or two
The Fitenta school dashboard: a Documents list showing every page staff have sent with the fields read and their status, and a People list of staff added by phone number
Schools' Admin ViewEvery page filed, and what state it's in
Advances on its own · swipe or scroll to browse
Why this travels

Beyond education use cases

A lesson plan is a working document, and every ministry has one. What transfers is not a model — it is the capture layer, built around a printed form with fixed fields, filled in by hand, produced daily and passed upward for review.

Pick a working document
Same page reader

ORIGINAL
Narrative
Fitenta · Prototype Data in images is fictional