Strategic processes. Tactical execution.

Atlassian solutions built for your business.

Tooling Tactics is an independent practice built for organizations that need real problem-solving, not just advice. I migrate, connect, and maintain your Atlassian environment until the software totally supports how your business runs. I execute the changes required to align your tools from sales to invoicing.

EU-based · Remote first, on site when the work needs it · Dutch, English, German

Data CenterAtlassian CloudLinear · ClickUp · ZendeskSales triggerInternal operationsInvoicingCRM · FinanceAdministrationAutomation · RovoInstance healthTooling TacticsATLASSIAN PRACTICEMigration TacticsCLOUD · DATA · ROLLOUTProcess TacticsSALES TRIGGER TO INVOICESupport TacticsADMIN · CONFIG · HEALTH

14 years

In and around Atlassian tooling

Product Owner, PMO, Senior Consultant, System Administrator

15+

1

Migrations and instance clean-ups

50 to 3,000 users

10+

Jira Cloud clean-ups & process alignments

Workflows, custom fields, permissions

1 Counted from 2013, instances over 50 users.

How it runs

Every engagement starts the same way: a short, fixed-scope first step and one clear decision at the end.

Week one is the last moment you can change course cheaply. I say so out loud, every time.

WEEK 1

Intake

Defining the problem as it actually exists, followed by an honest recommendation on which tactic fits best.

WEEK 1

Intake

Defining the problem as it actually exists, followed by an honest recommendation on which tactic fits best.

WEEK 1-3

Assess

Assessment, process discovery, or stack health check. You get a clear, actionable decision—not a slide library.

WEEK 1-3

Assess

Assessment, process discovery, or stack health check. You get a clear, actionable decision—not a slide library.

THEN

Execute

Migration waves, workflow restructuring, or monthly support—hands-on directly in the configuration.

THEN

Execute

Migration waves, workflow restructuring, or monthly support—hands-on directly in the configuration.

AFTER

Hand over or stay

Clean documentation handed over to named internal owners, or transitioning to a Support Tactics contract to keep it running.

Where the scope widens

Custom or unsupported Marketplace apps are the single biggest cause of delayed migrations. I evaluate them in week one, so the decision is yours early.

Start with a conversation, not a proposal

Thirty minutes. Bring the problem as it actually is: a messy instance, a stalled migration, a team without an owner.