Hello. The name is

Sanjiev

Arunasalam

Results-driven IT and Business Transformation professional with over 10 years of experience delivering technology-driven solutions that enhance operational efficiency, optimize business processes, modernize financial transaction ecosystems, and enable strategic business growth.

Two slots open from September 2026

Corporate room
Digital Transformation Leader & Strategist

Digital Transformation Leader & Strategist

98%

121+

successful roll-out projects

Working across four time zones

10+

Years working with tech leader, on corporate department and organizational level.

Background

Complex transformation is simple—provided your strategy is correct

I spent my early career inside agencies and consultancies optimizing legacy systems and engineering growth. Somewhere around the fourth multi-million-dollar strategy roadmap that sat on a shelf and never shipped, I started asking what the work was actually for. These days, I partner with fewer organizations, ask the awkward operational questions in week one, and stay embedded until the new architecture is fully live.

  • I analyze your customer support bottlenecks and legacy tech debt before I map out a strategy.
  • One veteran strategist on your initiative from the discovery call to full deployment — nothing gets passed down to junior accounts.
  • If I believe your proposed initiative is the wrong solution for your business, you hear it before you sign the contract.

In their words

What clients say once the invoice is paid.

Rated 5 out of 5

We briefed three studios before this one. August spent his first week inside our support inbox rather than a design file, then showed us the two screens costing us signups. Setup completion moved forty-four points.

Priya Raghunathan

Co-founder, Brightsill

Rated 5 out of 5

The handover is the part that surprised me. Our two engineers built the entire marketing site from his component library in eight days and never once had to message him.

Tomas Berger

CTO, Coalfield

Rated 5 out of 5

Fixed price, weekly demos, and in week two he told us to cut a feature rather than design it. That single conversation saved us a full quarter of engineering.

Elena Marchetti

Head of Product, Petrichor

Notebook

Things I keep having to explain.

FAQ

Asked before nearly every project.

How long does a project usually take?

A full product engagement runs six weeks end to end. An identity is three to four. A second opinion is one week. If your deadline is tighter than that, tell me early and I will say honestly whether it fits.

Is the price fixed?

Yes, wherever the scope is defined. One number, one payment schedule and a written list of what sits inside it. Anything outside becomes a conversation before work starts, never a surprise line on an invoice.

Can you work alongside our engineers?

That is the normal arrangement. I join your stand-ups, write specs in whatever format your team already uses, and stay reachable for a month after handover so questions get answered rather than guessed at.

What lands in my hands at the end?

Source files, a component library with every state documented, a token sheet, exported assets and a written spec covering behaviour and edge cases. Build engagements also include block patterns and a configured theme.json.

Do you take small pieces of work?

Sometimes. A single landing page, a pricing rewrite or a one-week review all fit comfortably. Anything larger tends to work better as a short sprint than as hours scattered across a quarter.

Who owns the work at the end?

You do, completely, once the final payment clears. Files transfer into your accounts rather than living in mine. I only ask permission to show the work publicly, and I will keep it private if you would rather.