Based in Atherstone · Remote support across the UK · Local visits by arrangement

IT Kabin Menu

How We Work

The same five steps apply to a five-page website and to a system used across an organisation.

Tell us what you need
Change requestExample
Agreed scope
Quotes, jobs, scheduling and invoices.
Requested change
Quotes that take a deposit when accepted, then jobs, scheduling and invoices.
Affects
Quote form, invoice template and customer portal.
Cost and timing
Confirmed in writing before work starts.

Awaiting your approval

ClientIT Kabin
When you want something changed, we write down the change and its effect on cost and timing, and you approve it before we start.

From first conversation to ongoing support

  1. Discovery

    How the work is done today, who is involved, what is getting in the way and what you want to achieve.

  2. Scope

    A written scope: what will be delivered, what it connects to, what is excluded, what it will cost and who is responsible for what.

  3. Build

    Built in stages that you can review, with your real content and data where possible.

  4. Test and hand over

    Checked against the scope on real devices, then delivered with documentation and access.

  5. Support

    Support, updates and changes on terms agreed before launch.

How we use AI tools

We use AI tools in design and development because they shorten build time, and a shorter build makes Bespoke Software practical for smaller budgets.

The tools work from the brief and scope agreed with you. Our own engineering standards set how the code is structured, secured, tested and documented, whichever tool produced the first draft, and work is ready only when it passes review and testing. We decide what to build, what to leave out, and when a simpler approach or an existing product would serve you better.

If your organisation has its own policy on AI-assisted development, tell us at the start and we will work within it.

Ownership, documentation and handover

Your systems should never depend on one person’s memory, including ours.

Documentation is proportionate to the project: for a small website, a short record of accounts and how changes are made; for software or managed IT, a fuller record of how the system is configured, deployed and supported. Through Process Documentation, we can write down your own procedures too.

Anything you buy outright is yours, including the source code, and you can take it to another supplier. Your content, data and accounts are yours too. We will never hold any of it to ransom. Before work starts, we confirm ownership in writing, including who holds the domain. At handover you receive the access and records you need.

With our Software Subscriptions, we own and run the applications, and you can export your data if you stop subscribing.

Handover checklistExample
  • Done: Accounts and access transferred to the client
  • Done: Domain, hosting and email recorded
  • Done: Backups tested and restore steps written
  • Done: Client shown how to request support and changes
  • To do: Client sign-off
ClientIT Kabin

Security and privacy

We collect only the information a project needs, keep credentials out of code and documents, apply updates and test the areas that commonly go wrong, such as forms and access controls. If your project handles personal data, we agree at the scoping stage who is responsible for what.

Start with a conversation

If we are not the right fit for your project, we will say so. The initial call is free, and there is no obligation.

Tell us what you need