NorthControl.

For consulting firms and agencies

Make your business
easier to operate.

I help consulting firms and agencies untangle workflows, understand project capacity and decide where AI or automation is worth the effort.

For consulting firms and agencies with roughly 10–50 people. Based in Norway. Working internationally.

A clearer view of the weekExample

One bottleneck. Three possible decisions.

Demand / capacity · hours per week

Analysis48 / 36 h
Coordination28 / 30 h
Delivery24 / 26 h
Analysis needs 12 more hours.

Delay scope, move work or add capacity. Total hours alone hide the constraint.

Synthetic figures · method demonstrationOpen analysis ↗
Experience & education
StatkraftBusiness analysis
EYExternal audit
NHHMSc · Business & Administration

Clarity before
another tool.

A useful starting point is a recurring problem you can describe: work waiting for an owner, conflicting demands or reporting that takes too long.

01 / Understand

Find where work gets stuck.

Map the process, the handoffs and the exceptions. Turn scattered information into an agreed view of what happens today.

DiscoverExamples and conversations
MapReality, including exceptions
PrioritiseValue, effort and risk
TestA small, reviewed improvement

See the thinking.
Inspect the work.

Two reconstructed professional examples and one fictional audit. Each is clearly labelled; no confidential employer data or claimed client savings.

01

Make competing demands visible.

Reconstructed professional example · synthetic data

A clear view of demand, usable capacity and the decisions needed when several projects depend on the same people.

At Statkraft, my work included resource coordination, project portfolio reporting and recurring resource meetings. This case illustrates how I would structure a capacity decision. The example, numbers and artefacts below were independently reconstructed; they are not an employer deliverable or a record of measured results.

From workload to a decision

The question

A project-based team has several concurrent commitments and a shared analyst. Every project looks manageable in isolation, but the same analyst is needed in the same week. The useful question is which commitments can be supported with the capacity actually available.

What I would establish first

Agree the planning unit and time horizon; separate committed demand from tentative requests; subtract leave and recurring operational work from available hours. Validate the demand with project owners and availability with resource owners. Missing or uncertain estimates remain visible rather than being treated as zero.

Illustrative weekly capacity view
RoleUsable hoursDemand hoursGap
Business analyst364812 short
Process specialist32302 spare
Team lead24222 spare
The management insight

Total capacity is 92 hours against 100 hours of demand, but the analyst has a 12-hour shortfall. Four spare hours in other roles do not solve that bottleneck unless the work is transferable. A portfolio average would hide the constraint.

Decision structure
  1. 01Confirm the conflicting commitments
  2. 02Check skills and dependencies
  3. 03Compare sequencing options
  4. 04Assign an owner and review date

Make the trade-off explicit

Illustrative decision log
OptionEffectCondition
Defer 8 analyst hoursShortfall becomes 4 hoursProject owner accepts revised sequence
Transfer 4 analyst hoursCloses remaining gapSplit 2 + 2 across the two roles, if skills match
Keep all commitmentsShortfall remains 12 hoursSponsor must resolve timing or capacity
Recommendation in this example

Validate the eight-hour deferral first. Split the remaining four hours across the process specialist and team lead, two hours each, only after checking skills, access and supervision needs. If the work is not transferable, record the unresolved four-hour gap and escalate the schedule decision. Do not silently assume overtime or interchangeable roles.

What the client receives

A capacity-and-demand table with named data owners, a short list of conflicts, a decision log and a repeatable update routine. A weekly update can focus on changed commitments; the decision meeting should focus on unresolved exceptions.

How I would validate value

Before changing the process, record how often conflicts are identified late and how long it takes to assemble a reliable view. After several planning cycles, compare those measures and ask resource owners whether the model reflects reality. No improvement percentage is claimed in this case.

What this demonstrates

Structuring uncertain operational data, distinguishing a capacity problem from a prioritisation problem, and presenting practical options for management. The historic evidence supports my participation in resource coordination and reporting; the model and decisions here are reconstructed examples.

Download this case study (PDF) ↗

02

Give every handoff an owner.

Reconstructed professional example · generic workflow

A workflow that makes ownership, required inputs and exceptions visible before anyone starts automating it.

At Statkraft, I worked on process modelling in ARIS and workshops with process owners. My earlier EY experience included business-process and internal-control work. This generic service-request example was reconstructed for the portfolio. It does not reproduce a Statkraft or EY process, client finding or internal document.

Map the work people actually do

The question

A service team receives work through email and informal messages. Requests may move to delivery before the scope is complete. The demonstration asks how to make the normal path, decision points and exceptions explicit without adding unnecessary administration.

Illustrative current state
  1. 01Request arrives
  2. 02Coordinator asks for missing details
  3. 03Team lead assigns work
  4. 04Delivery starts
  5. 05Scope questions return to the coordinator
How I would run discovery

Walk through one normal case and one exception with the process owner. Identify the trigger, required inputs, actual decisions, systems of record and handoffs. Separate observed steps from assumptions and proposed changes. Return the current-state map for validation before designing the future process.

Proposed future state
  1. 01Capture request in one queue
  2. 02Check required fields
  3. 03Owner approves scope and priority
  4. 04Assign delivery owner
  5. 05Deliver and record acceptance
Keep exceptions visible

Incomplete request: return to the requester with missing fields and an owner. Urgent request: record who authorises an exception before work starts. Scope change: pause the affected commitment until the accountable owner accepts the change. No silent bypasses or automatic approvals.

Turn the map into a working agreement

Illustrative ownership and control register
CheckpointAccountable roleEvidence
Required inputs completeCoordinatorChecklist in request record
Scope and priority agreedTeam leadApproval and rationale
Delivery owner acceptsDelivery leadAssigned owner and due date
Scope change acceptedTeam leadChange entry with decision
Work accepted and closedRequesterAcceptance recorded
What should be automated

Required-field checks, routing rules and reminders are candidates for simple rules once responsibilities are agreed. AI may help draft a request summary, but a person should approve scope and priority. The map establishes what a system must support; it is not proof that any integration has been built.

What the client receives

A validated current-state map, a future-state map, a process narrative, an ownership/control register, an open-questions list and implementation requirements. A simple flow diagram is sufficient for this example; formal BPMN can be used where the client needs that notation.

Acceptance and measurement

Ask each owner to confirm their inputs, decision and output. Test the proposed workflow with a complete request, an incomplete request, an urgent request and a scope change. Then measure missing-input rework and unowned requests against a baseline. This portfolio does not claim historical reductions.

What this demonstrates

Connecting stakeholder discovery, process documentation and control awareness. The professional background is documented in career sources; the specific workflow, register and recommendations are newly reconstructed.

Download this case study (PDF) ↗

03

Choose what is worth automating.

Fictional demonstration · no client engagement or measured results

An assessment for a fictional 18-person service business, with explicit assumptions, a ranked shortlist and a human-reviewed pilot.

Morrow Studio is an invented 18-person B2B service business. Every volume, time estimate, cost and projected benefit in this case is a demonstration assumption. No interviews were conducted and no system was deployed. The purpose is to show how I would evaluate operational improvements and challenge an AI business case.

Start with the operational problem

Fictional brief

Requests arrive in a shared inbox, project updates live in spreadsheets and meeting decisions are copied into task lists. The operations lead wants less chasing and clearer reporting. The assessment covers intake, weekly reporting and meeting follow-up; it excludes customer-facing decisions, payroll and payment approval.

Current workflow
  1. 01Read unstructured input
  2. 02Copy details into another tool
  3. 03Chase missing information
  4. 04Compile an update
  5. 05Owner reviews and acts
Proposed workflow
  1. 01Capture consistent source data
  2. 02Apply rules and completeness checks
  3. 03Draft a summary if useful
  4. 04Owner checks facts and decisions
  5. 05Publish an approved update
Prioritised opportunities
PriorityOpportunityJudgment
1Structured weekly reportingFix definitions and ownership; test rules first
2Request intake assistanceDraft and validate; do not auto-commit scope
3Meeting action draftsPilot only with approved data and consent
DeferAutonomous client repliesExternal error cost exceeds the case for speed
Why this order

Reporting is recurring, internally visible and easier to compare with a baseline. Intake has more varied language and exceptions. Meeting notes introduce recording and data-handling questions. The priority is based on readiness and risk as well as potential minutes saved.

A business case that can be challenged

Assumptions per working week
TaskVolumeBefore / afterEligible shareTime released
Intake40 requests8 / 5 min60%72 min
Reporting10 updates18 / 8 min80%80 min
Meeting actions12 meetings15 / 7 min75%72 min
Calculation

Time released = volume × (baseline handling time − future handling time) × eligible share. Future handling time includes human review. Tasks are defined as separate activities to avoid double-counting. Gross potential is 224 minutes per week. Subtract 45 minutes for ongoing maintenance: net potential is 179 minutes, or about 3.0 hours per week.

Capacity, not cash savings

At an assumed 48 working weeks, the base case releases 143.2 hours a year. This is available capacity, not a payroll reduction or realised financial return. Implementation effort, software costs and how the capacity would be used must be assessed before approval.

Sensitivity before a purchase
ScenarioGross benefit realisedNet min/weekNet hours/year
Conservative50% of base estimate6753.6
Base assumption100% of base estimate179143.2
What would invalidate the case

The workflow is infrequent, input data is unreliable, review takes as long as the existing task, exceptions dominate, or no owner can maintain it. In the conservative scenario, 45 minutes of maintenance still apply. Actual timings and eligible shares must be observed before relying on either scenario.

A small pilot with a clear stop rule

Pilot specification

Start with weekly reporting only. Use one agreed source table with project ID, owner, reporting period, status, next milestone and blocker. Check missing fields and duplicate project-period records with rules. AI drafting is optional; a template may be sufficient. Any draft must reference its source rows and label missing information.

Review and failure handling

The operations lead approves every update before publication. Missing owners, conflicting dates and unsupported statements go to an exception queue. No autonomous changes to project commitments or external messages. Keep an editable log and a manual fallback. Use only client-approved data and tools; redact sensitive inputs during testing.

Thirty-day sequence
WhenWorkDecision
Days 1–5Observe a full cycle; agree baselineIs the problem frequent and measurable?
Days 6–10Clean definitions; prototype one flowCan ordinary rules do the job?
Days 11–20Shadow-run alongside manual processAre outputs complete and supportable?
Days 21–30Review effort, errors and ownershipAdopt, revise or stop
Proposed acceptance criteria

Every published statement is supported by source data and approved by its owner. All required fields are present or explicitly flagged. Run at least two reporting cycles and compare handling time including review and corrections. Progress only if net effort falls, no critical factual errors reach publication and a named person accepts maintenance ownership.

Audit output

A process map, ranked opportunity list, assumptions table, benefit sensitivity and pilot brief. These are sufficient to make the next decision without committing to a large build. This is a fictional analysis demonstration; projected benefits are not client results.

Download this case study (PDF) ↗

A focused first engagement

One-Workflow
Operations Review

Bring one workflow that creates recurring frustration. Leave with a clear map, a prioritised improvement list and an actionable next step.

$490 USD · fixed scope

Five business days from complete inputs.
One consolidated revision included.

  • A 45-minute discovery session with the process owner
  • Review of up to three representative examples
  • Current and proposed workflow maps
  • Up to five prioritised improvements
  • A 30-minute findings discussion

Scope: one defined workflow. Software builds, production integrations and broader audits are scoped separately. Benefits are assessed, not guaranteed.

Discuss your workflow

About Audun

Business judgment.
Practical AI.

My background combines business analysis at Statkraft, external audit at EY and a master’s degree from the Norwegian School of Economics, specialising in Business Analysis and Performance Management.

At Statkraft, I worked with resource coordination, portfolio reporting and process modelling with business stakeholders. At EY, I worked with financial statements, internal controls and business processes.

Through my own projects, I use Claude and other AI tools to explore ideas, create prototypes and develop practical ways of working. I bring that experience to process assessment and workflow design, with clear boundaries around the technical implementation required.

Based in Norway. Remote collaboration in English and Norwegian.

Try the method.

Estimate the time a workflow could release, including human review and maintenance.

Open the workflow calculator ↗

Explore examples and practical guides

Before we start

A few practical questions.

Who is this for?

Consulting firms and agencies with roughly 10–50 people, several concurrent projects and recurring coordination or reporting problems. Smaller teams can also be a fit if the workflow is clearly defined.

What happens after the review?

You receive an editable map and prioritised actions. You can implement these internally, agree a separate follow-on scope with me, or use the findings to brief another specialist.

Will you build the automation?

The review determines what is worth doing and what implementation requires. Small prototypes may be appropriate. Production integrations, specialist engineering and ongoing operation require a separate scope and the right delivery capability.

What do we need to prepare?

Choose one workflow, identify its owner and bring up to three representative examples. We agree a suitable way to share information before any internal material is provided.

Can we work together outside Norway?

Yes. Delivery is remote in English or Norwegian. Scope, schedule and applicable taxes are confirmed in the written offer.

Start with the problem

Which workflow
is slowing you down?

Tell me what happens today, the tools involved
and what you want to improve.

Start a conversation

Meeting me through Upwork?
Please keep pre-contract communication there.