Systems · Processes · Automation

A company that runs without you in every process.

OneTenM is a boutique operational partner for growing companies. We build the Company OS — the processes, documentation and automation that turn a business held together by a few people into one that holds together on its own.

Two-week diagnosticEvery engagement starts with evidence, not a proposal
Field-testedBuilt in wind O&M and technical service, not in a seminar room
You own the systemProcedures, templates and workspace stay yours
PL · EN · NLGdynia, Poland — engagements across the Baltic and EU

What breaks

Growth does not fail on capability. It fails on operations.

The crews are competent, the clients keep calling, the order book is full. What stops working is everything around the work: who does what, on what information, and what has to be true before the job starts.

01
Everything routes through the founder

Decisions queue behind one person. Holiday, rotation or a bad week turns into delivery risk.

02
Readiness is assumed, not verified

Crews and subcontractors mobilise without documents, tooling or access confirmed — and the cost lands on the schedule.

03
The process lives in people's heads

Every job runs slightly differently. Onboarding a new coordinator takes months and quality depends on who picked up the phone.

04
Reporting is rebuilt by hand

Progress, hours and costs are retyped every week, arrive late, and rarely agree with each other.

What we build

The Company OS

Not a strategy document. The operating layer a company runs on day to day — designed around how your work actually moves, then installed, tested on live jobs and handed over.

Process map

How a job moves from enquiry to invoice, with owners and decision points named at each step.

Readiness gates

What must be true — documents, certificates, access, tooling — before anyone mobilises.

Document control

One place for procedures, RAMS, permits and templates, in versions the team trusts.

Workspace

ClickUp configured as the single place work lives: jobs, tasks, statuses, handovers.

Reporting

Progress, hours, cost and HSE assembled automatically instead of retyped every Friday.

Automation layer

Intake, quoting, follow-up and field forms wired together, with exceptions flagged rather than discovered.

What we do

Four areas. One operational backbone.

We work in operations, project delivery and automation — not branding and not sales. Every engagement lands in one or more of these, and each one ends in something your team uses on live work.

01

SystemsWhere most start

How the business actually works: roles, responsibilities, decision flows and the gates a job has to pass before it moves.

  • Operating model and role clarity
  • Readiness gates and handover points
  • Planning and resource allocation
02

Processes

Written down so the work does not depend on who picked up the phone: SOPs, playbooks, onboarding kits, document control.

  • Process map and SOP library
  • Document control, permits and method statements
  • Onboarding kit for new coordinators and crews
03

Automation

The parts of the business that should run without anyone: reporting, intake, follow-up and the admin that eats billable hours.

  • ClickUp, Make and integrations across the existing stack
  • Automated reporting and field forms
  • AI assistants for intake, quoting and follow-up
04

Project delivery

When the system has to be proven on a real project, we run it with you — campaign coordination, contractors, schedule and reporting.

  • Campaign and project coordination
  • Contractor readiness and interface management
  • Progress, cost and HSE reporting

How an engagement runs

Map → Gap → Translate → Implement

Deliberately boring, and the same every time. You see the evidence before you commit to the build, and you keep everything produced along the way.

Week 1–2Map

Inside the real process — site, office and the systems between them. What is documented, what people actually do, where the work stops.

You getProcess map and evidence pack
Week 2Gap

Findings ranked by cost and risk, with the rework, delays and disputes each one is responsible for. No generic maturity scores.

You getRanked gap list and fix plan
Week 3–6Translate

Fixes written as procedures, checklists and templates people will actually open — in the language the teams work in.

You getSOP library and workspace build
QuarterImplement

Run through one full campaign or quarter with your team, corrected against what really happens, then handed over.

You getTrained team and owner handover

What you walk away with

Artifacts, not advice

Documentation

  • Process map, end to end
  • SOPs for the recurring work
  • Readiness and mobilisation checklists
  • Permit-to-work and RAMS templates

Working system

  • ClickUp workspace configured to the process
  • Job, task and handover templates
  • Roles, owners and escalation paths
  • Reporting that builds itself

Handover

  • Team trained on the live system
  • Admin ownership transferred to you
  • Maintenance guide for the next 12 months
  • Optional quarterly review

Who we work with

Companies where the work happens in the field

Service and operational companies of roughly 10–100 people, where delivery happens in the field or on projects. Deepest experience sits in wind O&M and technical service — blade campaigns, major component exchange, industrial maintenance — but the operating problems travel well beyond it.

Wind O&M and service providers

ISPs, blade and component specialists, technician companies scaling past the point one coordinator can hold.

Technical service businesses

Lifts, HVAC, scaffolding, insulation and maintenance contractors running crews across sites and clients.

Suppliers to offshore developers

Companies entering Baltic offshore work that have to pass prequalification and survive the first campaign.

Project and field operations

Logistics, installation and professional services firms where every job is a small project with its own scope, crew and deadline.

Arkadiusz Piechowski, founder of OneTenM

Who is behind OneTenM

Built from inside the operation

OneTenM is run by Arkadiusz Piechowski: 14+ years in wind and industrial delivery, from blade operations at LM Wind Power and OEM service at Nordex to client-side O&M at Eneco Offshore. The approach comes from that work.

Wind O&M, from blade to asset owner

LM Wind Power, Nordex and Eneco Offshore: blade operations, OEM service coordination and client-side O&M on a 60-turbine offshore farm.

Permit-to-work at scale

TK Elevator / thyssenkrupp: procedures and contractor oversight across a 500+ unit portfolio, zero lost-time injuries for five years.

Automation that removed the retyping

Weekly operational reporting automated with Power Automate: about 30% less manual effort and better data accuracy.

Certified and multilingual

PRINCE2® v7, AgilePM® v3, VOL-VCA. Working in Polish, English and Dutch.

Engagement models

Three depths — Mini, Midi, Maxi

You pick the depth that fits the stage the company is at. Scope and price are fixed before anything starts.

Mini

Diagnostic sprint

2 weeks · fixed scope

One process mapped end to end, a ranked gap list and a fix plan you can run with or without us.

Midi

Company OS build

One quarter

Processes, document control, workspace and automated reporting built, tested through live work and handed over.

Maxi

Operating partner

Retainer · days per month

We stay in the operation — projects, contractors, reporting and the next automation — while your team grows into it.

Why OneTenM

Boutique by design

We work with a small number of companies at a time, and the person who maps your process is the person who builds it. No delivery team you never meet.

How is this different from a management consultancy?

A consultancy leaves a recommendation. We leave a working system: procedures, templates, a configured workspace and a trained team. If it does not survive a live campaign, it is not finished.

Do we have to change our tools?

Usually not. We build on what you already pay for and replace only what actively blocks the work. Where no backbone exists, we set up ClickUp because it covers delivery, documentation and reporting in one place.

What do you need from us?

Access to the real process for two weeks, one internal owner with authority to decide, and permission to talk to the people who do the work.

How do you price?

Fixed scope and fixed price for the diagnostic and the build; day rate for ongoing support. You approve scope before anything starts.

Do you work under NDA?

Yes. Client names and documents are never used as reference material without written approval.

Contact

Tell us what keeps slipping

If OneTenM is not the right fit, you will hear it in the first call rather than after an invoice.

Replies within one working day.