Delivered work, as delivered.
Everything on this page happened, described as what it actually was. Where the client has not supplied photography, the frame says so instead of showing a stock image. Original concept work is kept separately in the Workshop.
There is no custom software case study yet.
It would be easy to write one. A branding and print engagement can be dressed up as a transformation programme if nobody checks, and plenty of sites do exactly that.
Arohan has delivered brand, print, deployment and security work for clients, and that is what the three case studies above describe. It has not yet delivered a custom application or a process improvement engagement for a client, so there is no case study for one, and one is not going to be manufactured.
Until that work exists, the proof for those capabilities is of a different kind, and it is worth being explicit about what kind:
01 — Software engineering and delivery experience
Product ownership and systems analysis on government and enterprise platforms: large user bases, regulators paying attention, and real consequences when something goes wrong. The background is on the About page.
02 — Things you can open and use
This site is itself a build: a server-enforced download gate, signed tokens, verified accessibility, a documented deployment. The Workshop holds interactive tools that were designed, built and shipped rather than described.
03 — A method that is written down
Six stages, what each one produces, and what it costs to skip it. How we work is specific enough to be argued with, which is the point of publishing it.
What Arohan can build
- Internal business applications
- Customer portals
- Workflow systems
- Admin dashboards
- Approval platforms
- Request and intake systems
- Reporting dashboards
- API integrations
- Automated workflows
- Digital platforms
Software Engineering · Business Analysis · Product Ownership · Solution Design · Project Delivery
Why there are no percentages on this page
Numbers are captured at kickoff and again after delivery, because a result that was never baselined is an opinion. Where a figure does not exist, this site says what was delivered instead of estimating an outcome.
From here on, processing time, manual steps, handoffs and error rates get captured at kickoff, so that a future case study can say what changed and prove it. The full list is on How we work.