What onboarding involves

The fourteen days between signing up and your team working in it.

Onboarding is a fixed two weeks and it's done with you, not handed to you as a project. You don't need to appoint an internal owner or bring in an implementation partner.

Days 1–3 — your data comes across

Send whatever you already have: spreadsheets, a CAD folder, an export from your current system, or a mixture. It arrives as reviewable drafts rather than a blank vault you have to fill in. Nothing is committed until somebody on your side has looked at it.

The more representative the sample you send first, the better. Twenty or thirty parts covering your awkward cases is more useful than a thousand straightforward ones.

Days 4–10 — shaping it to how you work

This is where the configuration happens:

• Part numbering scheme, and whether people may enter their own
• Categories, and the fields and schedules each one needs
• Roles, permissions and access scoping
• Approval routes for changes
• Any custom development your setup needs

The included custom development

Up to ten hours of custom work is included at no charge. In practice this is usually a field your industry requires, an export shaped the way your ERP expects, or a report a customer asks for in a particular format. Raise it early in the fortnight rather than late.

Days 11–14 — your team starts

• Walkthroughs for the people who'll be in it daily, by role rather than one generic session
• The SolidWorks add-in installed on engineering machines
• Your first real change order run end to end, with us watching

What we need from you

Not much, but not nothing:

• Someone who can answer questions about how your numbering and categories should work
• An hour or two across the fortnight from whoever will administer it afterwards
• Your existing data, in whatever state it's in — cleaning it first is not required and usually wastes time