Industries · Government
They started online. They finished at the counter.
Plutonic builds government software for Indian departments — portals, file movement, and citizen status tied to the desks and systems you already run.
- The citizen started the form online and still queued at the counter
- The file is on someone's desk. Status is a phone call
- Back office re-types the PDF the portal already captured
- Scheme information lives in a circular nobody can find
Overview
What a department actually needs from software
Challenges
If this is your week, keep reading
The portal abandoned them
They started the application. They finished in a queue.
- Form dies halfway on a phone
- Status is 'pending' with no next step
- They take leave to stand at the counter anyway
The file is still paper
Desks re-key forms. Nobody knows which pile it's in.
- PDF printed, typed again, lost between sections
- Officer asks the citizen for a copy you already have
- Monday MIS is Excel someone built on Sunday
The people who need it most can't use it
Tiny text, English only, no keyboard path.
- Screen fails on a cheap Android
- No language the counter actually speaks
- Assistive tools bounce off the form
Upgrade stalled on a risk note
Useful change dies because audit and access weren't in the build.
- Shared logins on the counter PC
- No trail when a file moved
- Vendor left. Nobody can ship a patch
Solutions
What we put on the counter and the file
Solution 01
A service people finish
The mess
Applications stall across counters, PDFs, and a blank status.
What we put in
Guided steps, upload, and a staff queue that closes the loop — status the citizen can see.
- Next step on the phone
- Document in the file, not a photocopy pile
- Officer queue with an owner
Solution 02
The file moves without a peon chase
The mess
Departments drown in paper and duplicate entry.
What we put in
Case movement with a role, an SLA, and a trail — tied to the system you already run.
- Who has the file, today
- No re-typing the portal form
- Export audit will take
Solution 03
Find the scheme without a circular hunt
The mess
Citizens and staff can't find the current notice.
What we put in
Search over published content — with the source, not a guess.
- Cited from the gazette or SOP
- Escalate when it's not in the source
- Log of who asked what
Solution 04
A platform someone can still run next year
The mess
Launch, then stall under ops and a missing password.
What we put in
Monitoring, access, and handover — not a black box the vendor took home.
- Who can ship a patch
- Environments with a fence
- Runbook the department owns
Capabilities
What we actually build for departments
01
Portals people finish on a phone
Apply, status, download — in language and type size the counter already uses.
- Form that survives cheap Android
- Status with a next step
- Receipt they can show
02
File movement with an owner
Case across desks with an SLA and a trail — not a peon chase.
- Who has it today
- SLA the section can see
- Log audit will take
03
Find the form, not a rumour
Citizen and staff Q&A over published schemes — escalate when it's not in the source.
- Cited from the circular
- Human when it's an entitlement call
- Log of the ask
04
Intake off the scan
Classify and extract so the desk stops re-typing.
- Fields off the form
- Missing page flagged
- Officer on the mismatch
05
Logins that match the role
Officer, partner, public — not a shared password on the counter PC.
- Least privilege
- Session that dies when they leave
- Who opened the file
06
Talk to the other department without a CD
APIs and exchange that respect the boundary — no casual dump.
- Only the fields agreed
- Fence between systems
- No rip-and-replace as day one
07
Screens a citizen can actually use
Plain language, keyboard, contrast — built in, not a slide after go-live.
- Works on a small phone
- Language the counter speaks
- Doesn't fail a screen reader
08
Uptime the public notices
Environments, monitoring, a release that can roll back.
- Watch the form, not only the server
- Patch without a war room
- Handover the department owns
Use cases
Jobs a department will pay for
Get one service finished online
Pilot the form people abandon most. Expand when completion moves.
- One service first
- Status the citizen can see
- Roll out when counter load drops
Stop the PDF pile on the desk
Officer queue instead of re-typing.
- File with an owner
- Extract checked by a person
- Fewer 'bring another copy'
Kill the 'what's the status' call
Applicant sees the stage without a bus ride.
- Next step in plain words
- SMS or the portal, same story
- Desk handles the exception
Change without a big-bang rewrite
Phase, audit, rollback — the old system stays until the new one works.
- Coexist with legacy
- Trail from day one
- Cut over when the number moves
Recommended services
Where to start in our practice
Why it matters
Why departments stay with us
We talk files, not 'digital India'
If we can't name the counter and the circular, we don't belong in the kickoff.
- Completion rate
- File age
- No buzzword kickoff
Entitlements stay with an officer
We route and explain. Approvals stay with the person authorised.
- No unsupervised benefit call
- Log from day one
- Pilot on one service
We plug into what you already run
A portal that lives beside the file is a toy. We wire it in.
- No rip-and-replace as the pitch
- Counter + back office
- Handover you can staff
You can point at a number
Completion, file TAT, counter calls — not 'AI adoption'.
- Baseline before we start
- One owner per metric
- Expand when it pays
FAQ
Government questions
Yes. Deliverables, milestones, and the paper trail your purchase order needs. We don't pretend it's a startup SOW.
More industries
Explore other verticals
Map the highest-ROI service use case
Book a strategy call to prioritize one citizen service, file movement, or the counter queue.
Book Strategy Call