Some requirements have a clear beginning and end.
Some keep changing every month.
Some need several Vyasti capabilities working together over time.
And sometimes the first requirement is simply figuring out what should happen next.
Vyasti uses different engagement models so scope, responsibility, commercial structure and working rhythm can match the actual nature of the work.
The right model depends on what the work actually needs.
And recurring website maintenance should not be treated like a new project every time someone wants to change a page.
Different work has different characteristics.
A clear project structure usually makes more sense than an open-ended engagement.
The work may still be project-led, but the structure needs more milestones, dependencies and coordinated decisions.
The engagement has to coordinate strategy, identity and application rather than treat every output as unrelated work.
A repeating working rhythm usually fits better than repeatedly opening and closing small individual projects.
The structure needs room for recurring improvements, maintenance and changing digital priorities.
Several connected disciplines may need to move together over time, which requires a more integrated working structure.
The model is not the service.
It is the structure around how the service gets delivered.
Best for work with a clear scope, deliverable set and completion point.
The agreed scope typically defines:
You know what needs to be created.
The project has a clear objective.
The scope can be reasonably defined before production begins.
Priorities are expected to change continuously.
Requests will arrive every week.
The work spans an open-ended period.
Best for businesses that regularly need creative, digital, website, content or growth execution.
Rather than creating a new project proposal for every request, an agreed working capacity or priority structure supports ongoing needs.
Requirements recur.
Priorities change.
The team needs reliable execution access.
There is enough ongoing work to justify continuity.
There is only one clearly defined deliverable.
The requirement will disappear after delivery.
Best for organisations that need more than recurring production.
A retainer primarily solves:
A strategic partnership solves:
Work is organised around agreed priorities rather than one isolated deliverable. Relevant Vyasti capabilities can enter when needed. Longer-term context reduces repeated re-briefing. Business changes can inform what happens next.
Several workstreams are connected.
The business is changing quickly.
Brand, digital and communication decisions need alignment.
There is value in longer-term context.
Only one focused output is required.
The organisation does not need ongoing strategic involvement.
Sometimes the business knows the problem. But not the solution.
The requirement is ambiguous.
The investment could become significant.
Several possible solutions exist.
The team needs external structure before committing.
The execution scope is already clear and approved.
Not every ongoing relationship needs a creative retainer. Sometimes the website has already launched, the brand system exists and the main requirement is continuity.
Maintenance primarily asks:
A retainer usually asks:
The website is already live.
Updates are recurring but not full-scale projects.
Continuity matters more than continuous creative production.
Major redesign or strategic transformation is required.
The beginning, expected output and completion point are understood before production begins.
Continuity does not mean unlimited work. Priorities move through an agreed capacity and workflow.
The core system already exists. Support keeps it current and operational.
Start with what is happening.
EXAMPLE“We need a new website.”
The pages, functionality and broad requirement are understood.
A defined scope can usually be structured around a clear build and delivery outcome.
EXAMPLE“We need design and website support every month.”
There will be recurring requests and changing priorities.
Continuity and an agreed priority structure are more useful than repeatedly opening small individual projects.
EXAMPLE“We’re growing and brand, website, sales and content all need to move together.”
Several business systems need ongoing coordination.
The requirement is broader than recurring production. Shared context helps several connected workstreams move in the same direction.
EXAMPLE“We know something needs to change but don’t know what the project should be.”
The problem needs more definition before execution.
A scoped diagnostic phase can create enough clarity to define the right next move before committing to production.
EXAMPLE“The website is already live. We just need someone to keep it current.”
The system needs ongoing operational support.
The primary requirement is continuity, updates and upkeep rather than a new creative programme.
The pages, functionality and broad requirement are understood.
PROJECT-BASEDThere will be recurring requests and changing priorities.
MONTHLY RETAINERSeveral business systems need ongoing coordination.
STRATEGIC PARTNERSHIPThe problem needs more definition before execution.
DISCOVERY SPRINTThe system needs ongoing operational support.
MAINTENANCE & SUPPORTOne defined output is required.
PROJECT-BASEDThese are starting points.
The final model should follow the actual scope rather than force the requirement into a predetermined package.Bring us the situation.
We can work out the structure from there.
It should also establish how the work moves.
Pages · Screens · Assets · Documents · Videos · Systems · Outputs
Content · Assets · Feedback · Approvals · Technical access · Third-party requirements · Client dependencies
Stages · Expected sequence · Review windows · Dependencies · Launch / delivery targets
Review rounds · Consolidated feedback · Decision ownership · Changes beyond agreed scope
Project milestones · Monthly billing · Ongoing support arrangements · Other agreed structures
Files · Access · Documentation · Training where relevant · Maintenance · Support · Next-phase work
Pages · Screens · Assets · Documents · Videos · Systems · Outputs
Content · Assets · Feedback · Approvals · Technical access · Third-party requirements · Client dependencies
Stages · Expected sequence · Review windows · Dependencies · Launch / delivery targets
Review rounds · Consolidated feedback · Decision ownership · Changes beyond agreed scope
The commercial model is defined according to the agreed scope and engagement type. It may involve project milestones, monthly billing, ongoing support arrangements or other agreed structures.
Files · Access · Documentation · Training where relevant · Maintenance · Support · Next-phase work
Good scope is not bureaucracy.
It reduces avoidable ambiguity for everyone.
The label stays the same. The responsibility around it does not.
The amount of work, number of outputs and total surface area all affect responsibility.
Two deliverables can look similar in name while requiring very different levels of problem solving.
Research, architecture, positioning and decision-making can materially change the nature of the project.
Existing content may need restructuring, rewriting or creation before the design can work properly.
Photography · Video · Illustration · 3D · Motion · Specialist requirements
CMS · Forms · Integrations · Product behaviour · Migration · Special systems
Delivery pressure can change sequencing, resource coordination and review requirements.
The wider the responsibility across brand, digital, content, motion or growth, the broader the engagement becomes.
Or does the business need ongoing involvement after the initial delivery?
Established brand · existing content · straightforward build
More decisions · more dependencies · more production · more technical responsibility
We price the work required—
not the label attached to the project.
But it should not be chosen before the work itself is understood.
Before scope, commercials or delivery structure, we need to understand the business, requirement, current situation, intended outcome, timeline and constraints.
Scope clarifies what needs to be created, improved or maintained—and just as importantly, what is not required.
OUTSIDE CURRENT REQUIREMENT → NOT INCLUDED
Once the boundary is understood, Project, Retainer, Partnership, Discovery or Support can be considered against the actual requirement.
The model gains concrete terms around deliverables, responsibilities, timeline, commercial structure, payment schedule, review logic and support.
Approval is an alignment state: scope, responsibilities, commercials and the working structure are understood before production starts.
No signing animation. The important state is shared clarity around what happens next.
Access, assets, references, team coordination, schedule and project planning now move into Vyasti’s delivery workflow.
Business · Requirement · Current situation · Outcome · Timeline · Constraints
Create · Improve · Maintain · Exclude
Project · Retainer · Partnership · Discovery · Support
Deliverables · Responsibility · Timeline · Payment · Review · Support
Both sides understand the work, then production begins.
Context → Scope → Model →
Commercials → Kickoff.
Vyasti can work through defined projects, monthly retainers, strategic partnerships, discovery sprints and ongoing maintenance or support arrangements depending on the requirement.
Yes.
A project-based engagement is suitable when the expected outcome and deliverables can be reasonably defined before production begins.
Yes.
Retainers can support businesses that need recurring creative, website, communication, content, digital or growth work.
The exact capacity and responsibilities are defined in the engagement scope.
A retainer primarily provides continuity for recurring execution.
A strategic partnership usually involves broader business context and coordination across several connected areas over time.
The correct model depends on the nature of the work rather than the size of the client.
A Discovery Sprint is a focused engagement for requirements that need more clarity before full execution can be scoped responsibly.
It may involve audit, problem definition, architecture, prioritisation, concept direction or project scoping depending on the question.
Strategic Consultation is a focused conversation designed to clarify an important decision or problem.
A Discovery Sprint is a more structured piece of project work that may involve deeper review, synthesis and documented outputs.
Yes, where ongoing support is agreed.
The scope can include website changes, publishing support, page updates, technical fixes and other maintenance responsibilities appropriate to the platform and engagement.
Yes.
A business can begin with one defined project or discovery engagement and move into a larger relationship later if there is a genuine need.
There is no requirement to begin with the largest engagement model.
Yes.
If recurring needs become clear after the initial project, a separate ongoing engagement can be defined.
Priorities may change within the boundaries of the agreed retainer model.
The exact workflow, capacity and handling of work outside the agreement should be established before the retainer begins.
That depends on the specific commercial agreement.
Carry-forward rules, capacity, priority handling and billing should be defined explicitly in the retainer proposal rather than assumed.
Pricing depends on the actual scope, complexity, strategy required, number of deliverables, production requirements, technical needs, timeline, team involvement and level of ongoing responsibility.
Vyasti prepares commercials after understanding the work.
Not every engagement is long term.
A defined project or Discovery Sprint can have a clear completion point.
Longer-term commercial terms apply only where an ongoing engagement is agreed.
Material requirements outside the agreed scope should be discussed before additional work proceeds.
Depending on the change, the project may require reprioritisation, an expanded scope, a separate phase or revised commercials.
Start with:
You do not need to choose the engagement model yourself before contacting Vyasti.
Maybe it is one defined project.
Maybe your team needs consistent support every month.
Maybe several parts of the business need to move together.
Maybe the existing website simply needs someone to keep it working.
Or maybe the project still needs to be figured out.
Bring us the context.
We'll help structure the work around what actually needs to happen.Use the smallest structure that can responsibly support a clear, defined piece of work.
Use continuity when recurring requests and changing priorities genuinely justify an ongoing execution rhythm.
Use broader partnership structure only when several connected business priorities genuinely need shared context over time.
Use a diagnostic engagement when the problem matters but the right execution scope has not been defined yet.
Use maintenance and support when the main system already exists and the requirement is to keep it useful, current and operational.
The engagement should be no larger than the work actually requires.
START WITH THE REQUIREMENT.
