What to prepare

A little preparation before kickoff saves a surprising amount of time later. None of this is mandatory before you talk to us — it's what helps once a project is agreed. Don't worry if you don't have all of it; part of our job is helping you find or reconstruct it.

For any engagement

• A primary point of contact on your side who can answer questions and make decisions (or knows who can).
• The business goal behind the project, in plain terms — it helps us make the right trade-offs when details come up.
• Constraints we should respect — budget range, deadlines, compliance obligations, change-freeze windows.

For networking & infrastructure

• A rough inventory of existing equipment (switches, routers, servers, firewalls) and where it lives.
• Floor plans or site details for cabling, Wi-Fi, or surveillance work.
• Who currently manages your internet connection and domain/DNS, and how to reach them.
• Any existing credentials or admin access we'll need (shared securely — see Security & data handling).

For software & web projects

• Examples of systems you use today that the new software must work with.
• Any brand assets (logo, colours, fonts) and existing content.
• A sense of who the users are and the top tasks they need to accomplish.
• Access to relevant accounts (hosting, domain, analytics) when the time comes.

For cloud & migrations

• A list of the applications and data in scope.
• Current hosting details and who has access.
• Acceptable downtime windows for cutover, if any.

Sharing access safely

Never email passwords or keys in plain text. We'll set up a secure method to share credentials, and we only ask for the access a given task actually requires. If something looks over-scoped, push back — we'll explain why it's needed or find a narrower path.