Generic positioning
It lands on the founder / managing director first, well before it shows up in any number.
Marketing and creative services / Agencies and studios
Operloom designs and builds the connected system a web development agency runs on: the website, the CRM, the booking and follow up and the reporting, configured as one and handed over documented.
What earns the work is the work, the thinking behind it and who else has trusted it. What loses it is a system that cannot keep up with the interest it creates.
Primary conversion: Qualified enquiry, discovery call or proposal request
01B2B SME
Before any of this is a technology question, it is an operating question. These are the conditions a web development agency works inside, and the ones the build has to answer.
It lands on the founder / managing director first, well before it shows up in any number.
Left alone it becomes a reporting problem too: the record of what happened gets assembled afterwards, from memory.
Because new business competing with delivery for the same senior people, this one compounds rather than staying still.
Fixing it is rarely a tooling decision. It is a question of where the work is supposed to stop and who picks it up next.
None of this is unusual for a web development agency, which is exactly why it goes unaddressed for so long.
02B2B SME
A CRM only earns its place when it is the record everyone trusts. For a web development agency that means holding companies, contacts, opportunities, services, retainers, referrals and pipeline stages and nothing nobody maintains.
One record per client, holding everything anyone would otherwise have to go and ask for.
A lifecycle short enough that people update it, which is the only kind that stays accurate.
Open engagements with a realistic value and a next action, so the forecast means something.
Source captured on the first touch, because reconstructing it later is guesswork.
One accountable owner at every stage. Unowned records are treated as a fault, not a backlog.
Follow up scheduled when the engagement is created, not when someone remembers.
A short set of measures, defined once, produced the same way every period.
Access matched to role, which matters as soon as more than one person is involved.
03B2B SME
Written as it actually happens rather than as a funnel diagram. The steps that matter are the handovers.
A client finds the business through referral, positioning, awards and search for a named discipline.
They check whether this is the right business for them. This is what the work, the thinking behind it and who else has trusted it is for.
They send an brief. The form asks the questions that decide whether it can be scoped, and nothing else.
The brief is routed and qualified against the criteria that actually predict a good engagement.
A meeting is committed to a real slot, with the buffers and the preparation the work genuinely needs.
An estimate goes out with the scope written down, and its status is visible without anyone chasing it.
The engagement is delivered. What happened is recorded against the client, not in a separate note.
An invoice is raised from the same record, so what was agreed and what was billed cannot drift apart.
The next engagement is prompted deliberately, on the cycle this kind of work actually runs on.
04B2B SME
Discovery for a web development agency runs through referral, positioning, awards and search for a named discipline. The channels below are the ones that follow from that, and nothing is included because it is fashionable.
The foundations: crawlability, speed, structure and the markup that describes what this business is
Service, sector and problem led B2B content architecture
Optional for firms that rely on a defined local market
Answering what a client needs to know before they will make contact
LinkedIn led demand generation and proof based content operations
Search, LinkedIn and remarketing linked to qualified pipeline
Case studies, testimonials, references and proof governance
Campaign pages built from the same components, so they are fast to ship and consistent to measure
05B2B SME
The recommended build is B2B lead generation and authority website. The modules below are the ones this operating model needs, not a sitemap template.
06B2B SME
These are the workflows that carry the repeatable parts of a engagement. Every one of them has a human review point, because the useful automations are the ones people trust.
07B2B SME
Email only works when it arrives. Authentication and list hygiene come before anything creative, because a message in spam is worse than no message.
08B2B SME
Quoting, invoicing and payment are built as one path rather than three tools, because the gaps between them are where revenue goes missing.
A client asks for pricing with enough detail attached to answer properly.
Approval is recorded against the scope it approved.
Where a deposit is how the work is committed, it is taken at that point.
Raised from the agreed scope, not retyped from it.
Without a phone call, and reconciled automatically.
Available to the client rather than requested from you.
Visible on the record, so chasing is informed.
09B2B SME
Scheduling for a web development agency is where most of the avoidable loss sits. discovery, scoping and review meetings with qualification and routing.
Read from the real calendar, so double booking is not possible rather than unlikely.
Preparation and turnaround built into the slot, because a meeting is not only the time with the client.
The questions that decide whether the slot is right, asked before it is taken.
On the interval this kind of work needs, each one carrying a reschedule link.
A client can move a meeting without a phone call, which is how you find out early.
A clear policy applied consistently, with the slot released for rebooking.
To the right person and the right location, using rules rather than judgement.
Handled properly wherever the work crosses them.
10B2B SME
Every one of these already exists in some form, usually as a tool somebody chose alone. The build is mostly about the lines between them.
Where a client first finds the business.
The pages a client reads before deciding to make contact.
Qualifying questions asked once, at the point of enquiry.
Every client, every engagement and who owns it.
Real availability for a engagement, with the preparation time it needs.
Estimates and invoices raised from the agreed scope.
Payment taken and reconciled against the record.
Operational and lifecycle messages that arrive and are logged.
The rules that move work between systems, with human review where it matters.
What a client can see and do without contacting anyone.
Campaigns tracked through to the record they produced.
The measures a web development agency is actually run on.
Who is told, when, and what they are expected to do about it.
11B2B SME
Not every business needs every capability, and pretending otherwise is how implementations get expensive. This is the mix a web development agency typically needs, split by how load bearing each part is.
CRM setup and data model supports web development agency businesses by helping to generate qualified b2b demand
Pipeline and lifecycle design supports web development agency businesses by helping to generate qualified b2b demand
Lead routing, scoring and follow up supports web development agency businesses by helping to generate qualified b2b demand
Website build or redesign supports web development agency businesses by helping to generate qualified b2b demand
Service and landing pages supports web development agency businesses by helping to generate qualified b2b demand
Brand identity system supports web development agency businesses by helping to generate qualified b2b demand
Sales and marketing materials supports web development agency businesses by helping to generate qualified b2b demand
Email infrastructure and deliverability supports web development agency businesses by helping to generate qualified b2b demand
Email campaigns, nurture and reminders supports web development agency businesses by helping to generate qualified b2b demand
Analytics and conversion tracking supports web development agency businesses by helping to generate qualified b2b demand
Dashboards and attribution supports web development agency businesses by helping to generate qualified b2b demand
Technical and on page SEO supports web development agency businesses by helping to generate qualified b2b demand
Content strategy and copywriting supports web development agency businesses by helping to generate qualified b2b demand
Documents, forms and e signature supports web development agency businesses by helping to generate qualified b2b demand
Workflow automation supports web development agency businesses by helping to generate qualified b2b demand
Security, privacy and maintenance supports web development agency businesses by helping to generate qualified b2b demand
12B2B SME
Better systems do not guarantee a commercial result, and nobody should promise one. What they do is remove specific failure points. These are the ones that matter for a web development agency, and the measures that would show whether the change worked.
Asking the qualifying questions at the point of enquiry, so the engagement is scoped before anyone spends time on it.
Measure: Qualified leadsGiving clients the confirmations, reminders and status information they would otherwise have to ask for.
Measure: MeetingsMaking the second engagement as deliberate as the first, rather than leaving it to whoever remembers.
Measure: ProposalsBeing findable for the terms a client actually uses, rather than the ones the business uses internally.
Measure: Win rateKnowing what is committed, what is quoted and what is at risk, without rebuilding the picture by hand each month.
Measure: PipelineTaking the repeatable parts of the engagement out of somebody's head and putting them into a workflow that runs whether or not it is a busy week.
Measure: Recurring revenue and source13B2B SME
Reporting is built around the decisions the business actually makes. For a web development agency that is a short list, which is the point.
Measured from the record rather than reconstructed at month end.
Broken down by source, so the number leads somewhere.
Defined once and written down, so it means the same thing next quarter.
Reviewed alongside the stage it depends on, not in isolation.
Broken down by source, so the number leads somewhere.
Tracked as a trend, because a single period rarely means anything.
14B2B SME
What exists now, what it costs to run, and where a engagement currently loses time.
Decisions made once, in writing, so the build is execution rather than a series of small arguments.
Delivered in stages that each stand up on their own, rather than one launch that has to go perfectly.
Integrate the platforms so CRM, proposals, project management, accounting, email, calendar and analytics behave as one system.
Documentation aimed at whoever runs this next year, which may not be whoever commissioned it.
Tracking, dashboards and definitions, so the effect is checkable rather than asserted.
Improvement as a standing habit rather than a second project.
15B2B SME
Concrete deliverables, not projected commercial results. What each one achieves depends on how it is used after handover.
16B2B SME
Recommended starting scope
SME Revenue Operations
A starting scope rather than a fixed package. The plan page sets out who it is for, the core deliverables, the modules, the integrations and the measures.
Core measures
Scope varies with what already exists, so we do not publish a figure. Tell us what you have and you will get a scoped proposal with the assumptions written down.
17B2B SME
The categories this operating model usually has to connect. Naming a category is not a claim of partnership, certification or reseller status.
18B2B SME
Consent, data processing, claims and client confidentiality.
That is a factual summary of the areas that tend to apply, not advice. Requirements vary by jurisdiction and change. We build to what your advisers confirm applies, and we implement it properly: consent capture, retention, access control, audit trails and secure handling.
19B2B SME
Carefully, and within our lane. Consent, data processing, claims and client confidentiality. We build to what your advisers tell us applies: consent capture, retention rules, access control, audit trails and secure handling. We implement requirements. We do not interpret them for you, and we will say so rather than guess.
You get the documentation, the workflow map and the training, because the point is that you own it. Ongoing support is a separate arrangement rather than an assumption: some businesses take a maintenance and improvement retainer, others take the handover and run it themselves. Both are fine, and we will tell you which one we think fits.
By measuring the stages rather than only the close. Source, brief quality, meeting rate, proposal rate and stage ageing all move long before revenue does, and they are the ones that tell you whether a change helped. Attribution is set up to survive a cycle measured in months rather than days.
Less than most people expect, but not nothing. Access to the platforms, a decision maker who can settle scope questions in the same week they are asked, and someone who knows how the work really runs, which is rarely the same as how it is written down. Content and assets where you have them. We write what you do not.
Availability comes from the real calendar, not a copy of it, so a engagement cannot be booked into a slot that is already gone. Discovery, scoping and review meetings with qualification and routing. Every booking writes back to the client record, so the diary and the pipeline are the same story.
The scope starts from how this kind of business runs rather than from a package. In practice that means B2B lead generation and authority website, a CRM holding companies, contacts, opportunities, services, retainers, referrals and pipeline stages, and the booking and follow up around it. The nearest starting point in our catalogue is SME Revenue Operations, which is a scope to argue with rather than a fixed list.
It depends on how much already exists and how clean it is. A build is sequenced so that something useful goes live early rather than everything landing at once: the CRM and brief capture first, because that is where work is lost today, then the site, then the automation, then reporting. We give a timeline after a scoping conversation, not before one.
Often, yes, and it usually makes the project smaller. A maintainable site is better connected than replaced: brief capture that carries its source, tracking that survives, and a clean handover into the CRM. The CRM question is whether it can hold companies, contacts, opportunities, services, retainers, referrals and pipeline stages without being fought. If it can, we configure it properly. If it cannot, we say so and explain what migrating would actually cost you in time and disruption.
The first conversation is a scoping one: what exists, what it costs to run, and what would have to be true for qualified enquiry, discovery call or proposal request to happen more often. No obligation and no prepared deck.