Cases
What the work looks like in practice. Client names are anonymised; sectors are real.
Energy: architecture for an energy markets domain
Context. A major energy company in Sweden, with a business area for energy markets.
Problem. The applications in the energy markets domain have to keep up with both business change and regulation. Without one architect owning the domain, each change is decided on its own and the standards drift.
What we did. Since 2022, Poush Digital has provided the domain architect for energy markets. The work covers the architecture of the domain’s applications against business and regulatory requirements, keeping the architecture standards current, and coordinating with the teams that build and run the systems. Poush also helped the IT leadership team develop its strategic roadmap and ran workshops to align employees with the strategic goals.
Result. [To be added]
Energy: [second case title]
Context. [To be added]
Problem. [To be added]
What we did. [To be added]
Result. [To be added]
Poush Digital: a back office run by agents
Context. Poush Digital is a small company with the same bookkeeping as any other: receipts, supplier invoices, card bills and payments, all needing to reach the accountant correctly and on time.
Problem. Manual filing and reconciliation take time every month, and a missing receipt or a mistyped payment reference is easy to miss.
What we did. We built a set of agents with clear limits and a human checkpoint:
- Receipts and invoices are read, classified and filed, and recorded in an expense register.
- Card bills are reconciled against the filed receipts, and lines without a receipt are flagged.
- A payment list is produced on a schedule, with check digits on account numbers and payment references validated before anything is paid.
- A person approves every payment. The agents never pay anything themselves.
Result. [To be added]
Why it matters for you. It is a small system with the same parts any serious agent needs: a clear scope, the right tools, checks on the output, and a person who signs off.
Poush Digital: agent tooling for architecture assessments
Context. Architecture assessments usually start with weeks of reading code and documentation, and still only cover a sample.
Problem. In an organisation with many repositories, nobody can hold the whole picture in their head, and documentation rarely matches what the code does.
What we did. We built agent tooling for AI conversations across multi-repo codebases. It lets us ask questions of a whole IT landscape, such as which services depend on a given integration or where a data entity is written, and get answers traced back to the code.
Result. [To be added]
Why it matters for you. Your current-state assessment starts from what your systems actually do, covers all of them, and can be rerun when they change. See How we work.
Earlier experience
Before founding Poush Digital, Shahram worked on enterprise architecture and digitisation in healthcare, public transport, and logistics and shipping. Those are not Poush cases, but they shape how he approaches each new engagement. See Industries.
Have a similar problem?
Request a 30-minute call and tell us what you are facing.