Digital & Automation Assessment

One assessment. A complete picture of what to do next.

Most organizations do not have a technology problem — they have a visibility problem. Systems accumulated over years, processes held together by spreadsheets and heroics, and no single view of what is actually running the business. The Digital & Automation Assessment fixes that in two weeks: a structured diagnostic that maps your systems, documents how work really flows, and identifies where automation pays back — with a sequenced roadmap your leadership team can approve and act on.

This is the front door to working with HarjTech. It is fixed in scope, fixed in timeline, and it ends with decisions, not a bigger consulting engagement. Whether you proceed with us or take the roadmap to your own team, you leave with clarity.

Who it is for

CIOs, VPs of IT, Directors of IT and Applications, and operations leaders at organizations of 100+ employees who suspect their teams are doing too much manual work — and want evidence before committing budget.

Why visibility comes before automation

Automation layered on top of an undocumented process does not fix the process. It makes the chaos faster. Many organizations have learned this the expensive way: a workflow automated exactly as it ran, including the approval steps that existed because of an org chart from five years ago, the manual checks that duplicate what the system already validates, and the handoffs that only exist because two departments never agreed on an owner. The assessment separates process problems from tooling problems before anything gets automated. Sometimes the right answer is to simplify the process and automate nothing. Sometimes the right answer is a small automation that removes a single bottleneck. Sometimes the right answer is a larger program. The assessment tells you which, with evidence, before you spend.

That is what makes this diagnostic different from a vendor demo or a tooling recommendation. It is not selling a platform. It is answering a question: where is manual work actually costing you, and what is the most valuable thing to do about it?

What the roadmap is for

The roadmap is a decision instrument, not a report. It sequences the work into horizons — what to do now, what to do next, and what belongs in a larger program later — with dependencies, owners, and effort ranges for each item. Leadership can use it in budget planning, IT can use it to defend priorities, and operations leaders can use it to see where their pain points rank against everyone else's. Because it is documented, it survives staff changes. The reasoning behind each priority is written down, so a new leader does not have to re-litigate decisions that were already made on evidence.

What happens after the assessment

Three paths are all legitimate outcomes. HarjTech can implement the roadmap through scoped build packs. Your internal team can implement it — the documentation is written to be executable by a competent team that was not in the room. Or you can defer some or all of it, with a clear picture of what deferral costs. The assessment is designed to be useful in all three cases. Its value does not depend on buying the next engagement.

Approach: two weeks, structured around decisions

Week 1 — Discover

We confirm scope and stakeholders, then map your systems and walk through your highest-cost processes with the people who run them. By the end of week one you have a draft systems inventory and a long list of candidate automations.

Week one runs on a tight rhythm. Day one is a kickoff with your sponsor and day-to-day contact: scope is confirmed, stakeholders are named, and access to people is arranged. The next several days are discovery sessions — typically 60 to 90 minutes each — with the process owners and the people who perform the work. In parallel, the systems inventory is built system by system: what exists, who owns it, what it costs, what it connects to. A mid-week check-in with your sponsor keeps the work on track and surfaces anything that needs a decision early. By the end of the week, the inventory is in draft and the candidate list is long — deliberately long, because the scoring in week two is what narrows it.

Week 2 — Quantify and decide

We score each opportunity, build the ROI model, sequence the roadmap, and present findings in an executive readout. You leave with a plan and a decision — not a deck that needs another deck to explain it.

Week two is analysis and decision. Each candidate is scored against the rubric, and the ROI model is built with stated assumptions. The roadmap is sequenced — quick wins, foundations, larger programs — with dependencies and owners. A draft is reviewed with your sponsor before the readout, so there are no surprises in the room. The executive readout is a facilitated working session: findings are walked through, each item is discussed on its evidence, and the group records approve, decline, or defer for every item. You leave with a decision log and a roadmap your team can execute.

What the client experiences

Your team stays involved without carrying the assessment: a sponsor, one day-to-day contact, and focused access to process owners — typically a 60 to 90 minute session each. The ask on your side is small and specific. There is no homework, no data-gathering project, and no disruption to daily work. HarjTech organizes the evidence, performs the analysis, and facilitates the decisions. Your people contribute what only they know — how the work actually runs — and get back a roadmap they helped shape.

Decisions along the way

Three decision points keep the assessment honest. At kickoff, scope and stakeholders are confirmed — what is in, what is out. At the mid-point check-in, the candidate list is reviewed and any process that does not belong is cut. At the readout, every roadmap item gets an explicit decision. Nothing drifts. Nothing is assumed.

Capabilities this service draws on

• Process discovery and business analysis. Mapping how work actually flows — including the exceptions, workarounds, and handoffs that never appear in policy documents — and turning that into documentation a team can act on.
• Systems and integration mapping. Inventorying applications, ownership, cost, and data flows, including the shadow systems that only surface through interviews with the people who use them.
• Automation opportunity analysis and ROI modelling. Scoring candidates on volume, error rate, effort, and payback, and building business cases with stated assumptions that finance can test.
• Microsoft 365, SharePoint, and Power Platform advisory. Knowing what the platform you already own can do — so the roadmap recommends automation on tools you have before it recommends anything new.
• Workflow design with Power Automate. Designing approvals, notifications, exception handling, and audit trails that work the way your process actually runs, not the way a template assumes it runs.
• Data flow and integration architecture. Understanding how systems connect, where data is duplicated or re-keyed, and where an integration removes manual work at the source instead of patching it downstream.
• Change and adoption planning. Because a roadmap nobody adopts is a document. Adoption planning identifies who is affected, what changes for them, and what support they need to make the change stick.

How these capabilities work together

An assessment is not seven separate skills applied in sequence. It is one diagnostic motion: discovery feeds mapping, mapping feeds scoring, scoring feeds the ROI model, and the ROI model feeds the roadmap. Platform knowledge matters because recommendations land on tools the client already owns — the roadmap rarely requires a new platform. And adoption planning matters because a roadmap nobody acts on is a document. The capabilities combine into a single outcome: a client who knows what to do, why, and in what order.

Engagement model

Fixed-scope diagnostic. The assessment stands alone — you commit to nothing beyond it. If the roadmap identifies work worth pursuing, HarjTech can continue with defined implementation packs or an advisory retainer. The assessment fee is confirmed on the scoping call; the roadmap itself is yours to execute with us or on your own.

Fixed-scope means the deliverables, the timeline, and the investment are agreed before work starts. There is no hourly meter and no scope creep by invoice. You know on day one what you will receive: the systems inventory, the process maps, the scored opportunity list, the ROI model, the sequenced roadmap, and the executive readout.

Stopping after the assessment is a designed outcome, not a failure mode. Many clients take the roadmap to their internal team, and the documentation is written to make that work — process maps a new hire could follow, business cases finance can test, and a roadmap with owners and dependencies already assigned.

If you want HarjTech to implement, the roadmap becomes the backlog: each item is scoped as a defined implementation pack with its own acceptance criteria, and you can proceed item by item. If you want guidance while your team executes, an advisory retainer keeps a senior advisor in the conversation — reviewing designs, unblocking decisions, and keeping the roadmap on track. The scoping call determines which shape fits: the assessment itself is the same in every case, and the next step is your decision, made with the evidence in front of you.

How the relationship starts

It starts with a scoping call: your situation, the processes in scope, the stakeholders, and the timeline. HarjTech confirms scope and investment, and the assessment begins with a kickoff. From kickoff to readout is two weeks. You know the deliverables, the dates, and the decision points before work starts — and you know that stopping after the assessment is a legitimate outcome, not a failure mode.

The problem: you are running the business on invisible work

Ask three managers how a core process works and you will get three different answers. The official process lives in a policy document. The real process lives in spreadsheets, inboxes, and one employee's head. This is how organizations end up paying for automation they do not need, while the manual work that actually costs money goes untouched.

The symptoms are easy to recognize:

• Manual work everywhere. Teams re-key data between systems, chase approvals by email, and rebuild the same reports every month.
• No systems inventory. Nobody can list every application, who owns it, or what it costs — so every decision is a guess.
• Shadow processes. Departments build their own workarounds because the sanctioned tools do not fit how they work.
• Automation without a case. Tools get bought on vendor promises, deployed, and quietly abandoned because no one quantified the return first.
• Change fatigue. Staff have seen enough failed initiatives to resist the next one — even a good one.

The cost is not just inefficiency. It is decisions made on bad information, key-person risk when the one person who knows the process leaves, and budget spent on the wrong fixes.

The hidden cost of invisible work

Invisible work charges in four currencies. The first is rework: data entered twice, reports rebuilt, approvals re-chased, corrections applied to work that was already done. The second is delay: cycle times measured in weeks for processes that should take days, because every handoff waits in someone's inbox. The third is error: manual steps are where mistakes enter, and mistakes in approvals, data entry, and reporting carry consequences that range from embarrassing to regulatory. The fourth is heroics: the quiet reliance on one or two people who hold the process together through memory, relationships, and overtime. Heroics feel like dedication. They are actually a single point of failure with a burnout timer.

None of these show up as a line item. They show up as a team that is always busy and never caught up, a budget that never stretches far enough, and a leadership team that senses something is wrong but cannot point to what.

Why internal teams cannot see it

Proximity blindness is real. The people who built the workarounds are the same people asked to document them, and nobody writes down the workaround they are slightly embarrassed about. Managers describe the process as it is supposed to run. The people who actually run it describe it as it runs — if someone asks them directly, with no stake in defending the current state. An outside diagnostic has no history with the process, no attachment to the tools, and no reason to soften the findings. That distance is part of the value.

The cost of doing nothing

Drift compounds. Every month adds another workaround, another spreadsheet, another undocumented dependency. The eventual fix does not stay the same price while you wait — it gets more expensive, because there is more to untangle and more people whose habits have hardened around the workaround. The cheapest time to map the estate is now. The second cheapest time is after the next incident makes it unavoidable, at a higher price and under pressure.

What is included

• Systems inventory. A documented map of your core applications, integrations, data flows, and ownership — the first time most organizations see the full picture in one place. Each entry records what the system is, who owns it, who uses it, what it costs, what it connects to, and what state it is in. Shadow systems surface through interviews — the tools departments adopted on their own — because the inventory is built from conversations with the people who do the work, not just from IT's asset list. The inventory is delivered as a living document your team can maintain, not a snapshot that expires the day it is delivered.
• Process discovery. Structured interviews and walkthroughs of your highest-cost processes, documented as they actually run — not as the policy says they should. Sessions run with the people who perform the process, not only the managers who oversee it, because the gap between the documented process and the real one is where the cost lives. Each walkthrough captures the steps, the handoffs, the exceptions, the workarounds, and the points where work waits. The result is a process map in plain language that a new hire, an auditor, or a successor could follow.
• Automation opportunity scoring. Each candidate process scored on volume, error rate, effort to automate, and payback — so priorities are evidence-based, not opinion-based. The scoring rubric is transparent: you see the criteria, the weights, and the score for every candidate, so you can challenge a ranking instead of taking it on faith. Some candidates that look attractive on the surface score low because the volume is small, the exceptions are many, or the underlying process needs simplifying first. That discipline is the point — it is what keeps the roadmap honest.
• ROI model. A plain-language business case for each recommended automation: what it costs, what it saves, and how fast it pays back. The model states its assumptions openly — current cost per transaction, time per step, error rates, build and ongoing costs — so finance can test them. It separates hard savings (hours removed, errors avoided, licenses retired) from softer benefits (faster cycle times, better visibility) and never blends them into a single inflated number. Sensitivity is shown where it matters: what changes the ranking if volumes shift or effort runs higher than estimated.
• Sequenced roadmap. A phased plan — quick wins first, foundations next, larger programs last — with owners, dependencies, and effort ranges. Quick wins are the automations that pay back fast and build momentum. Foundations are the fixes that later work depends on — a data cleanup, an integration, a governance decision — that deliver little visible value alone but unlock everything after them. Larger programs are sequenced last, when the organization has proof and the foundations are in place. Dependencies are mapped explicitly, so nothing is scheduled before the work it depends on.
• Executive readout. A facilitated session with your leadership team to walk through findings, agree priorities, and decide what happens next. The readout is structured around decisions, not presentation: each item is presented with its evidence, its cost, and its payback, and the group records approve, decline, or defer for each one. You leave with a decision log, not just a deck.