# How a fixed monthly budget becomes a marketing and tech scope

Canonical page: https://aryehalgorithms.com/resources/marketing-and-tech-support-on-a-fixed-budget · Updated 2026-09-15

On a fixed budget a company gets a scoped department rather than a package: a written list of which marketing and tech functions run, at what cadence, on which systems, fitted to the monthly figure the company names. Aryeh Algorithms fits the scope to the figure by choosing a lead function, setting its cadence and naming the systems it needs, then adding supporting functions by dependency rather than by appetite. The scope is reviewed every month, so when the budget grows or shrinks, what runs changes with it. Whatever the size of the scope, the client receives the weekly summary, the client portal and direct access to the CEO.

## A fixed budget buys a scope, not a package

With a package, the price is fixed and the work is whatever the package contains. With a scope, the budget is fixed and the work is chosen to fit it. The difference matters more than it sounds. A package is designed for an average company, so part of it is spent on things you do not need and part of what you do need sits in a higher tier. A scope starts from your business and your number. Nothing is in it that you did not choose, and nothing that fits is left out because it belonged to a different tier.

The scope is a short written document. It names the functions the department runs, the cadence at which each one produces its output, the systems it is connected to, the work your own team keeps and the review at which all of this is checked. It is agreed before any build starts and it is the reference for the whole engagement. When a question comes up about whether something is included, the answer is in the scope rather than in a sales conversation someone half remembers.

Because the scope is written against a monthly figure, it is also a plain description of what that figure buys. That is the honest answer to the question in the title. How much support a company gets depends on how the number is spent, and the scope is the record of how it is spent. The rest of this piece explains how each line of that record is decided.

## How the functions are chosen

The department has a defined set of functions: strategy, research, content, campaigns, demand generation, lead generation, outbound, sales enablement, marketing operations, analytics and technology. A fixed budget does not buy all of them at once, and it should not try to. Spreading a limited figure across every function produces a thin version of each, and thin functions do not settle. The first question in scoping is which single function would move your pipeline most if it ran well.

The answer differs by company. A business with a working website and no outbound needs outbound, and the research that feeds it. A business with inbound demand it cannot route needs marketing operations before anything else. A business whose sales team is fielding the wrong conversations needs lead generation and qualification tightened first. The discovery conversation exists to find that lead function, and the scope is built around it.

The functions after the first are chosen by dependency rather than by appetite. Outbound needs research. Campaigns need content. Every function needs analytics to be read and technology to run on. So a scope that names one lead function usually carries a smaller share of two or three supporting ones, sized to serve the lead function rather than to stand on their own. That is how a modest figure covers more ground than a bare list of function names would suggest.

## Cadence and systems set the size of each function

Once the functions are chosen, two settings decide how much of the budget each one uses. The first is cadence: how often the function produces its output. Content can be drafted, approved and published on a weekly rhythm or a monthly one. Research can refresh a target list continuously or on a fixed schedule. Outbound can run one sequence to one segment or several in parallel. Each of these is a choice, written into the scope, and each moves the cost of the function up or down.

The second setting is systems. A system that already works costs the scope a connection and a test. A system that is missing costs a build, and the build takes its place in the scope as a line with a cadence of its own: forms in the first month, routing in the second, tracking once there is traffic to measure. Sequencing the build is what lets it fit a fixed figure. This is where the tech support in the question lives. It is not a second service with a second budget. It is the part of the scope that keeps the marketing functions running on sound systems.

The trade-off between the two is visible when the scope is drafted. A higher cadence for the lead function may mean connecting one system now and another later. A missing system that has to be built may mean a slower cadence for the first months. These choices are made with you, in the open, so the scope reflects your priorities rather than a default.

## The scope is reviewed every month

A fixed budget is only useful if what it buys is checked. Every month the scope is reviewed against what happened. The weekly summaries from the month are the starting point: what each function produced, what changed in the pipeline, what was held for a decision and what the systems reported. The review asks a short set of questions. Did the lead function do what it was scoped to do? Has it settled enough to add the next function? Is the cadence right? Has anything changed in the business that should reorder the list?

The review ends with a revised scope, versioned in your portal beside the one it replaces. Sometimes nothing changes. Often something small does: a segment is retired, a cadence moves, a supporting function takes a larger share because the lead function now depends on it more. The budget stays the same across these changes. What moves is how it is spent, and the record of each move sits next to the work in the portal so what changed and why is one document rather than a thread to reconstruct.

The monthly review is also where the scope is protected from drift. A department that runs for a year accumulates requests, and each request is reasonable on its own. Without a review they are absorbed quietly, and the scope stops describing what runs. With a review, a request is fitted into the scope, traded for something else, or scheduled for when the budget can carry it. Either way it is written down.

## What grows and what is cut when the budget changes

Budgets change, and the scope is designed to change with them without a renegotiation. When the figure grows, the addition follows the same order the scope was built in. First the lead function is given more room: a higher cadence, a second segment, another channel. Then the next function on the dependency list is added properly rather than as a supporting share. Then the systems that were deferred are built. Growth is spent on depth before breadth, because a function that already works makes better use of an increase than a new function that has not settled.

When the figure shrinks, the order runs in reverse and the same principle holds. Cadence is reduced before a function is removed, because a function running slowly keeps its data, its integrations and what it has learned, while a function switched off loses momentum that is expensive to rebuild. Supporting functions are narrowed to what the lead function strictly needs. Deferred builds stay deferred. Only when cadence and breadth have been reduced is a function paused, and it is paused rather than dismantled, so it can be restarted when the budget returns.

Both directions are decided at the monthly review, or sooner when a change cannot wait, and both are written into the scope with the reason attached. You are never guessing what was dropped. What the budget no longer covers is named, and so is what it would take to bring it back.

## What every client receives, whatever the size of the scope

The scope decides what is spent on functions. A separate layer of the engagement is fixed, is not deducted from that spend, and is worth knowing before you name a figure. It is the same for the smallest scope and the largest, and the rest of this section names what sits in it.

The weekly summary is the same document at every size; a smaller scope means fewer lines in it, not a thinner view of the operation. The client portal holds the work as it happens: the scope itself, every task, approval and recommendation, and the activity history behind them. Direct access to the CEO is the same commitment at every size. Messages in the portal reach Aryeh, the CEO of Aryeh Algorithms, at any hour, and are answered directly. There is no account manager at one budget and the CEO at another.

Supervision, maintenance and the running of the workflows are not lines in the scope, so they are not reduced when it narrows. They are the cost of operating a department at all, carried by the engagement rather than by any function. The workflows keep their own schedule; that is a fact about the system, separate from the commitment that you can reach the CEO around the clock.

## What to bring to the first conversation

You do not need to arrive with a scope. You need three things: the monthly figure you can sustain, an honest picture of what you run today, and what your sales team says is missing. The figure matters most. A scope drafted against a real number is useful from the first month. A scope drafted against a number that might be available later is a plan for a department that does not exist yet, and it will be redrawn as soon as the real number is known.

From there the discovery conversation finds the lead function, the written scope sets cadence and systems, and the monthly review takes over. The drivers of scope and what every operation includes are set out on the pricing page. This piece has explained how they are applied to a fixed figure. The remaining step is the conversation, and the person on the other side of it is the same person who will run the department.

## Questions

### Does a smaller budget mean a smaller team on the account?

No. A smaller budget means a narrower scope: fewer functions, a slower cadence or fewer systems connected. It does not change who you work with. The weekly summary, the client portal and direct access to the CEO are the same for every engagement, and a narrower scope is drafted, reviewed and run by the same person as a wider one.

### Can the scope change in the middle of a month?

Yes, when a change touches the lead function. A segment that stops converting, a launch that moves or a sales team reporting the wrong conversations is raised in the portal and the order is reset at once, with the revised scope dated the same day. Changes that can wait are gathered for the monthly review so the scope does not drift. Either way the change and its reason are written into your portal.

### Is technology work part of the same monthly figure?

Yes. Connecting your CRM, website and email, and building missing forms, routing or tracking, are lines in the same scope as the marketing functions. Advertising spend and software licences sit outside it as third-party costs. Inside the figure, technology is sized like any function: working systems are connected first, missing pieces are built in sequence, and a build that does not fit this month’s figure is deferred rather than dropped, and added first when the figure grows.

## Related

- [How the CEO partnership runs every engagement](https://aryehalgorithms.com/solutions/ceo-partnership)
- [How the partnership works, from discovery to optimization](https://aryehalgorithms.com/how-it-works)
- [What the technology function builds and maintains](https://aryehalgorithms.com/ai-marketing-department/technology)