Norrvik Logistics — Fleet Ops Rollout
A complete fictional CRM environment, built from scratch to show fluency with real client-facing systems.
Overview
Norrvik Logistics is a fictional freight and logistics client I built out to practice a different flavor of project management than my Asana work — a phased operational rollout, structured in ClickUp, where the sequencing itself is the hard part.
Approach
- 01
Set up a ClickUp workspace with a dedicated space for the client engagement, separate from other active projects.
- 02
Built a Project Roadmap view grouped by workstream, so every task's place in the bigger rollout was visible at a glance.
- 03
Sequenced the roadmap realistically: stakeholder interviews and KPI requirements first, then vendor evaluation, an onboarding SOP, a depot pilot, and only then full rollout and training.
- 04
Assigned priority levels — Normal, High, Urgent — so the roadmap reflected what actually needed attention first, not just a flat task list.
In Practice
Beyond Norrvik: Multiple Client Engagements
The same ClickUp fluency applied across different fictional clients — each with its own workspace, task structure, and views suited to the work.
Meridian Data Solutions — CRM Migration
Meridian had been running sales and support out of a spreadsheet for years, and it was starting to show — duplicate contacts, fields nobody remembered the purpose of, no real audit trail. They wanted to move to HubSpot before the next sales cycle, but didn't have anyone in-house who could own the migration end to end.
I set up the project in ClickUp so both sides could see exactly where things stood. Kickoff came first — getting alignment with their team on scope and a hard deadline, since sales didn't want to be mid-migration during a busy quarter. From there it was an audit of the existing data: I found roughly 180 duplicate contact records and a dozen fields that hadn't been touched in years, so we made the call to archive rather than migrate those to keep the new instance clean.
The trickier part was field mapping — matching Meridian's custom fields to HubSpot's contact, company, and deal properties, and flagging anything with no clean equivalent for the team to weigh in on. A few fields, like an internal renewal-risk score, didn't have an obvious home, so those went back to the client as a decision point rather than something I guessed at. Once the mapping was signed off, I built out the import process, ran a test batch, then moved to full migration and a round of user acceptance testing with the sales team before go-live — followed by two weeks of daily check-ins to catch the small stuff before it became a problem.
What this shows: I can take a messy, years-old system and turn it into a clean migration plan without losing institutional knowledge along the way — and I know when to make a judgment call versus when to loop the client in.
Solvane Health Group — Patient Portal Launch
Solvane wanted a patient-facing portal for booking appointments, requesting prescription refills, and messaging care teams directly — but healthcare projects come with a layer most others don't: compliance can't be an afterthought.
I started with a requirements workshop alongside their clinical ops and IT leads to nail down what "must-have" actually meant for launch versus what could wait. From there, I mapped out the core user flows — booking, refills, messaging — before any of it touched a compliance review, because there's no point getting legal sign-off on something that's going to change shape in wireframing.
Compliance coordination ran in parallel with the day-to-day project work rather than blocking it, which kept things moving without cutting corners on the review Solvane's IT team needed. Alongside that, I put together a support ticket triage process so the team had a plan for handling login issues, booking errors, and urgent access requests from day one of the pilot — rather than figuring it out reactively once patients were already using it. We ran a two-week beta with a single pilot clinic before touching the wider rollout, which is where most of the real bugs and friction points surfaced. Launch comms — patient emails, in-clinic signage, staff talking points — came last, once we actually knew the portal was stable enough to promote.
What this shows: I know how to sequence a project so the risky, compliance-heavy pieces don't become bottlenecks, and how to build support infrastructure before launch instead of scrambling after.
Outcome
This project pushed me to think in phases and dependencies rather than just tasks — pilot before full rollout, requirements before vendor selection. It's also given me hands-on fluency with ClickUp specifically, alongside Asana, so I can adapt to whichever tool a client already runs on.
Interested in working together?
Let's talk about how I can help your team run smoother.
Get in Touch