Catalyst B2B

IT consulting

The software your business runs on, built properly.

Websites that convert the traffic you paid for, web and mobile apps for your clients, and internal tools that replace the spreadsheet three people fight over. Scoped, built and handed over.

Book a 20-minute call See the rest of what we do

Available on its own. You do not have to be a lead generation client to hire us for this.

Scoped and priced per project, before we start
Fixed Scoped and priced per project, before we start
You own the code, the repo and every account
Yours You own the code, the repo and every account
Typical build, from one site to a full internal system
2–12 wk Typical build, from one site to a full internal system
Built on standard tools another team could pick up
No lock-in Built on standard tools another team could pick up
01 Why we do this

It started as a bottleneck we kept running into.

Halfway through most lead generation engagements the same thing happens. The meetings start landing, the firm gets busier, and something behind the sale cannot cope. The website loses half the people we send to it. Quoting lives in one person’s inbox and takes three days. Scheduling is a spreadsheet that two people overwrite. The CRM has never been set up, so nobody can tell you what is in the pipeline.

For a while we pointed at it and left. Then we started fixing it, because pointing at a problem your client cannot solve is not much of a service.

So IT consulting is a real part of what Catalyst does now, and plenty of firms hire us for it with no outbound attached. Same people, same approach: scope it honestly, build the smallest thing that solves it, hand it over so you own it.

What we get called in for

  • A site that gets traffic and converts almost none of it
  • A manual process somebody repeats forty times a week
  • Two systems that do not talk, reconciled by hand every Friday
  • A client-facing product the firm has been meaning to build for two years
  • A CRM nobody trusts, so the forecast is a guess
02 What we build

What we build

The work we take on

Four kinds of project. Most engagements are one of them; some start as one and reveal another.

  • Websites and landing pages

    Fast, accessible, written to convert, and built so your team can edit it without calling us. If we are also running your outbound, the site is built around the promise the outreach made.

  • Web and mobile applications

    Client-facing products and portals, from first screens through to launch. Web apps, and native or cross-platform mobile where the phone is genuinely the right place for it.

  • Internal business software

    Quoting, scheduling, dispatch, job tracking, approvals, inventory, timesheets, reporting. The unglamorous systems a services business actually runs on.

  • Integration and automation

    Making the CRM, the accounting system, the forms and the inbox talk to each other, so the Friday afternoon of copying between them stops happening.

  • Reporting and dashboards

    One place that answers the questions you keep asking: what is in the pipeline, what did it cost to get, where is the job, and what is unbilled.

  • Sensible technical foundations

    Hosting, backups, access control, monitoring and documentation. Boring, cheap to do at the start, and expensive the first time it is missing.

03 How it runs

How a build runs

Fixed scope, fixed price, and a working thing at the end rather than a discovery phase that eats the budget.

  1. A scoping session, before any number.

    What the process looks like today, who touches it, where it breaks, and what the workaround costs you in hours. Often the answer is smaller than what you came in asking for, and we will say so.

  2. A written scope and a fixed price.

    What we are building, what it does, what it deliberately does not do, and what it costs. Anything outside that is a separate conversation rather than a surprise on the invoice.

  3. Build in short passes you can see.

    Something usable in front of you every week or two. You catch the misunderstanding in week two, when it costs an afternoon, rather than at handover.

  4. Test it against the real work.

    Run with real data, real jobs and the people who will actually use it. Software that only works in a demo is not finished.

  5. Handover, and you own everything.

    Code in your repository, every account in your name, documentation for how it works, and a walkthrough for the people using it. Support afterwards is available and optional, never a lock.

04 Projects

The shapes these projects usually take

Rough guides from the work we take on, so you can see where you sit before the call.

Project What it typically includes Usual length
Marketing site rebuildStructure, copy support, design, build, analytics, and the handover so you can edit it2 to 4 weeks
Internal tool, single processOne workflow replaced end to end: forms, records, permissions, notifications, reporting4 to 8 weeks
Client-facing web appAccounts, the core product surface, billing or scheduling if needed, admin side8 to 12 weeks
Mobile appThe app itself, the backend behind it, store submission and release8 to 12 weeks
CRM setup and integrationPipeline configured to your real process, data migrated, systems connected, team trained2 to 3 weeks
Automation of a manual processThe specific hand-off automated, with the exceptions handled rather than ignored1 to 3 weeks

Ranges, not quotes. The scoping session produces a fixed number against a written scope, and that is the number on the invoice.

05 How we build

Built to be handed over, not to keep you dependent.

A lot of small agencies build in a way that makes leaving expensive: their hosting, their accounts, a framework nobody else uses, and no documentation. It is good for retention and bad for the client.

We build the opposite way on purpose. Every project ends with you owning the code, the accounts and the knowledge, on tools any competent developer could pick up. If you want us on retainer afterwards, we would rather it was because the work was good.

  • Code in a repository you own, from the first commit
  • Hosting, domains and third-party accounts in your name and on your card
  • Standard, widely used tools. No framework only we understand
  • Written documentation, and a recorded walkthrough for the team
  • A fixed price against a written scope, agreed before we start
06 Fit

What we take on, and what we do not

We are a good fit for

  • B2B and services firms who need a specific system built well
  • Replacing a spreadsheet or a manual process that has outgrown itself
  • A first version of a product, built small enough to learn from
  • Websites that have to convert rather than just look current
  • Firms who want to own what they paid for

Look elsewhere for

  • Large multi-year enterprise programmes with a dozen stakeholders
  • Day-to-day IT support, help desk and device management
  • A team to inherit and maintain someone else’s undocumented codebase
  • Work priced below what doing it properly costs
07 Questions

Questions about the build work

Do we have to be a lead generation client?

No. Plenty of IT consulting clients have never bought outbound from us. It works well together when a firm buys both, because the site and the CRM get built around what the outreach actually promised, but it is genuinely a standalone service.

Who writes the code?

Our build team, with Akshay leading the technical side and staying on the project from scoping through handover. Where a project needs a specialist we bring one in and tell you we have.

What do you build on?

Whatever the project actually calls for, chosen from mainstream, well-supported tools. We will tell you what we are proposing and why during scoping, and part of the test is whether another team could pick it up later.

What happens after launch?

A support window is included so the first weeks of real use are covered. After that you can take a small ongoing arrangement, call us when you need something, or take it in house. All three are fine and we will not make the third one hard.

Can you fix something a previous developer left behind?

Sometimes. We will look at it honestly and tell you whether it is worth repairing or cheaper to rebuild the part that matters. We will not take on maintaining a large undocumented codebase we did not write.

How do you price it?

A fixed price against a written scope. If the scope changes, we price the change before doing it. No open-ended day rates, and no discovery phase that spends a quarter of the budget before anything is built.

Also from us

The rest of what we do

Next step

Tell us what the workaround is costing you.

Bring the process that eats your team’s week, or the site that gets traffic and no enquiries. Twenty minutes is usually enough to tell you roughly what it takes to fix and whether it is worth fixing at all.

Book a 20-minute call See all services