“In progress” is just a polite word for delayed. Paperwork should not take a lifetime. Promises do not clear backlogs. Software does. Paperwork is where efficiency goes to die.
Software for offices that still run on paper. Built in Bhubaneswar, works offline, speaks Odia, and the code is yours.
Software for offices that still run on paper.
01Process improvement
Not really a huddle if you have the right tool
A week in a district office. Catch the three tools and watch the office change around you.
Clear a week of office work
Space or click to jump, twice to flipTap to jump, twice to flip
Week cleared
0.0s
An office drawn behind the runner. It starts grey and buried in paper, with every screen switched off. Each tool you catch changes it: the screens come on, the paper goes, and by Friday the room is calm, light and digital.
- Open 100 unread emails
- Print the attachments
- Stamp and file the copies
- Enter it all in the register
- Two years of back records
- Chase four departments
- Re-type the same details
- Read ten pages of handwriting
- Reconcile two registers
- Photocopy for the file
- The monthly return, by hand
- Find last quarter on a pen drive
- Tally the figures twice
- Type the report from scratch
- Software The screens come on and the back records stop being paper.
- Automation The monthly return files itself.
- Digitisation The rest of the week rolls into one system.
02Who it is for
Offices that run on records and deadlines.
If the work depends on a register, an approval chain or a monthly return, it is built for you.
If the work runs on registers and approvals, it is built for you.
- District administrationCollectorate, sub-division, block
- Urban local bodiesMunicipalities and NACs
- Banks & institutionsBranch-funded civic projects
- Education & healthColleges, hospitals, training
- Boards & PSUsAuthorities and corporations
03How it works
You show us the work. We build around it.
Tell us, and we build it
You have the requirement, the forms and the rules. We turn them into working software and hand it over.
You bring the forms and rules. We build it and hand it over.
We tell you what is best
Describe what is going wrong. We come back with the options and what each one costs, and we build once you approve.
Tell us the problem. We come back with options and costs.
- 01
Understand
Sit with the team and map the work as it runs.
We map the work as it runs. - 02
Design
Turn the process into screens, rules and outputs.
Screens, rules and outputs. - 03
Prototype
You use it before it is built, and say what is wrong while changing it is still cheap.
You try it before it is built. - 04
Build
Working software every week, shaped by what you told us.
Working software every week. - 05
Hand over
Train the team. Leave the code, data and documentation.
Training, code and documents.