Skip to content
Dispatch

6 min read

A new company's digital setup checklist

Set up a company's domain, brand, website, email, access and operational tools with clear ownership. A practical checklist using the Attenta build as an example.

About this piece

Stage
Published
Published
2026-10-01
Tags
Company setup, Digital foundations, Integrations

The short answer

Set up a new company's digital foundations in dependency order: check the name, secure the domain under company control, establish account access and email, then build a consistent brand, website and social presence. Put records and everyday operations in place before launch. Finish with a handover that lets the business run without depending on one supplier's login.

You do not need every tool on day one. You need clear ownership, a working way for customers to contact you, and somewhere reliable to keep the resulting work. Use the sequence below to separate launch essentials from later improvements.

1. Check the name before committing to the identity

Agree the legal entity, any trading name, and how that relationship will appear on customer-facing material. Check relevant company registers, domain availability, social handles and possible trade mark conflicts before spending heavily on design. Finding an available domain is not legal clearance.

Name a business decision-maker to approve the identity. Record the checks, choices and unresolved questions. Company formation, trade marks, tax, contracts and funding eligibility need advice appropriate to your jurisdiction and circumstances. This is a digital setup checklist, not universal legal or financial advice.

2. Secure the domain and establish account ownership

Register the domain through an account the business controls, rather than a supplier's personal account. Record the registrar, renewal date, billing owner and who can change DNS records. Enable renewal reminders and check the payment method. Domain loss can affect both the website and company email.

Set up named administrator accounts with multi-factor authentication (MFA), limited permissions and a documented recovery route. Keep recovery material securely, not in the handover document itself. Avoid circular recovery where access to the domain depends solely on an email address on that same domain.

3. Put email and access in place before public launch

Choose the email and collaboration platform around how the team works. Create individual accounts and shared addresses for enquiries or administration where needed. Configure the provider's email authentication records, then test sending, receiving and replies from outside the organisation.

  • Assign someone to check each shared inbox, with cover for absence.
  • Require MFA and use a password manager instead of shared passwords.
  • Give suppliers only the access needed for their work.
  • Document how accounts are added, recovered and removed when someone leaves.

The business should retain administrative control even when setup is outsourced.

4. Build one identity across the website and socials

Agree the practical brand kit: logo files, colours, type choices, tone of voice and reusable document templates. Then apply it to the website, email signatures and the social channels customers actually use. Reserve useful handles without promising to maintain every platform.

The website should explain the offer, who it serves and what to do next. Check contact details, business disclosures, accessibility, mobile usability and the privacy information appropriate to the data you collect. Decide who owns content updates and enquiries. A polished page is not ready if its contact form delivers to an unmonitored inbox.

5. Organise records before connecting operations

Choose an authoritative home for customer details, documents and work status. Define access, retention and backups before copying personal information into several tools. Keep company paperwork, contracts, invoices and programme applications organised with an owner and a review date.

Map the first customer journey: enquiry, response, agreement, delivery and follow-up. Allocate each handoff to a person. Start with manual steps where the rules are still changing. If established tools need to share data, explore systems integrations with clear data ownership rather than introducing another disconnected spreadsheet.

A real example: Attenta's company foundations

The Attenta Partners company build story documents Wacky Works Digital's work from zero: naming, domain, brand, a website built from scratch, social channels, setup paperwork, funding support and startup programme applications. The operating setup includes Microsoft 365, Azure virtual machines, deployed AI models and agents running 24/7.

6. Use a launch and handover checklist

Ask the business owner to confirm these items with whoever delivers the setup:

  • Ownership: domain, hosting, email and social accounts are company-controlled.
  • Access: named administrators, MFA, recovery and supplier removal are tested.
  • Public journey: mobile pages, links, forms and enquiry replies work.
  • Records: storage, permissions, retention and backup responsibilities are clear.
  • Costs: subscriptions, renewals, billing owners and any expiring credits are listed.
  • Handover: brand files, configuration notes and operating instructions are accessible.
  • Accountability: each inbox, system and recurring check has an owner and deputy.

If an essential account or enquiry route has no owner, resolve that before launch. Defer optional channels and automation until the core operation works. To discuss a coordinated setup, send a company foundations brief through Transmission with what exists, what is missing and who will run it.