Discover · Analyse · Strategise · Plan · Execute · Optimise
Process & Guidelines

About Process & Guidelines

How we work, and how we collaborate. The first half of this page explains our six-step engagement process.  The second sets out the project guidelines that keep every engagement clear, transparent and professional from initiation to closure.

6

phases, applied to every engagement

48h

turnaround on documented decisions

1

accountable lead from start to scale

Section 01 — Our process

Our six-step engagement process.

Every phase produces a documented output, an agreed decision and a metric that carries into the next. Nothing moves forward on opinion alone.

01

Discover

1 – 2 weeks

We begin with evidence: leadership interviews, market context, customer insight and a full audit of what already exists. Nothing is recommended before it is understood.

Outputs

  • Stakeholder interview synthesis
  • Current-state audit
  • Market and competitor scan
  • Constraint register

Who is involved

Founder, leadership team, engagement lead

Decision at close

Agreement on the real problem being solved — and what is out of scope.

02

Analyse

1 – 2 weeks

Data is modelled — unit economics, funnel performance, competitive whitespace and operational capacity — to isolate where value is created and lost.

Outputs

  • Commercial data model
  • Channel and funnel diagnostics
  • Unit economics baseline
  • Opportunity sizing

Who is involved

Intelligence analyst, engagement lead

Decision at close

The two or three levers with the highest return on attention.

03

Strategise

2 – 3 weeks

Findings become decisions: positioning, priorities, target segments and the commercial thesis the entire programme will serve.

Outputs

  • Positioning statement
  • Messaging architecture
  • Brand and category narrative
  • Strategic thesis document

Who is involved

Strategy director, brand lead

Decision at close

A single written thesis that every downstream decision is measured against.

04

Plan

1 – 2 weeks

Strategy is sequenced into an executable roadmap with owners, dependencies, budgets, timelines and the metrics that define success.

Outputs

  • Phased roadmap
  • Resource and budget plan
  • Measurement framework
  • Risk and dependency map

Who is involved

Engagement lead, delivery leads

Decision at close

Sequencing: what ships first, what waits, and what we deliberately do not do.

05

Execute

4 – 12 weeks

Our delivery teams build — brand systems, platforms, automations, campaigns — to a documented standard and an agreed release cadence.

Outputs

  • Brand system and assets
  • Website or product build
  • Campaign and content systems
  • Analytics instrumentation

Who is involved

Design, engineering, content and performance teams

Decision at close

Go-live readiness, signed off against the measurement framework.

06

Optimise

Ongoing

Performance is reviewed against the model. What compounds is scaled, what underperforms is corrected, and the roadmap is revised on evidence.

Outputs

  • Monthly performance review
  • Experiment backlog and results
  • Refreshed forecasts
  • Quarterly strategy reset

Who is involved

Performance lead, intelligence analyst

Decision at close

What to scale, what to fix, and what to retire in the next cycle.

How we work

The operating principles behind the method.

Research reports and analytics on an executive desk
Evidence before execution

Everything in writing

Scope, assumptions, decisions and changes are documented. Nothing important lives only in a conversation.

One accountable lead

A single engagement lead owns the outcome across strategy and delivery. You never have to translate between teams.

Fixed review cadence

Weekly working sessions, monthly performance reviews and a quarterly strategy reset — scheduled at kickoff.

Metric before build

No deliverable enters production until the metric it is meant to move has been agreed and instrumented.

Cadence

What the working rhythm looks like.

Week 0

Kickoff, access provisioning, stakeholder map and success criteria signed off.

Weekly

60-minute working session: progress, blockers, decisions required from you.

Fortnightly

Written progress note with completed outputs, upcoming work and open risks.

Monthly

Performance review against the measurement framework, with recommendations.

Quarterly

Strategy reset — revisit the thesis against market movement and new data.

Section 02 — Guidelines

Project Guidelines

Every successful project is built on clarity, transparency and mutual collaboration.  These guidelines keep delivery smooth and professional for both parties.

Guideline 01

Working Together

Consultants reviewing a project proposal with a client
Proposal · Advance · Kickoff

Projects begin only after the agreed advance payment is received. The advance is non-refundable once the project has commenced, because planning, resources and execution are allocated specifically to the engagement. Scope is governed by the approved proposal — additional requirements, feature requests or revisions beyond that scope are treated as separate engagements with revised pricing and timelines.

Project Initiation & Payment Terms

Projects begin only after the agreed advance payment is received. Once work commences, the advance is non-refundable.

  • A project is confirmed on written acceptance of the proposal and receipt of the agreed advance.
  • The advance reserves delivery capacity and covers planning, resourcing and mobilisation allocated specifically to your engagement — it is strictly non-refundable once work has commenced.
  • Milestone payments are stated in the proposal. Delivery may pause where payments remain outstanding.
  • Quoted amounts exclude taxes, third-party licences, media spend and platform subscriptions unless stated.

Scope of Work

The approved proposal governs scope. Anything not expressly listed sits outside the engagement.

  • Deliverables, inclusions and assumptions are defined in the accepted proposal.
  • Additional requirements or feature requests are treated as separate engagements with revised pricing and timelines.
  • Where scope is uncertain, we document the assumption in writing before work begins.

Change Requests

Changes to agreed direction or specification are quoted separately with a revised timeline.

  • A change request is any instruction that alters agreed scope, direction, specification or platform.
  • Each change request is estimated in writing — cost, timeline impact and dependencies — before it is actioned.
  • Reopening a previously approved deliverable constitutes a change request.

Revision Policy

Each deliverable carries a defined revision allowance built on consolidated feedback rounds.

  • Revisions are structured rounds of consolidated feedback, not open-ended iteration.
  • Feedback from all stakeholders should be collected and submitted together by your nominated point of contact.
  • Approved deliverables are considered final and move into production.
Guideline 02

Collaboration & Project Delivery

Delivery is a shared responsibility. Timely approvals, timely content and written confirmations keep the timeline intact.

Client Responsibilities

Timely approvals and content submission keep the engagement on schedule.

  • Nominate a single point of contact authorised to approve deliverables.
  • Provide content, data, credentials and access when requested.
  • Return consolidated feedback within the timeframes in the project plan.

Communication Standards

Written approvals through Email or WhatsApp keep every decision traceable.

  • All approvals are confirmed in writing via Email or WhatsApp.
  • Working sessions are scheduled; ad-hoc requests are logged and prioritised.
  • Communication takes place through agreed channels during stated business hours.

Project Timeline

Timelines are built on agreed scope and timely client input.

  • Estimated durations are stated per phase at kickoff.
  • Delays in approvals, content or access automatically extend delivery timelines.
  • Revised dates are re-issued in writing whenever a dependency shifts.

Project Suspension

Inactive projects may be placed on hold and rescheduled.

  • A project inactive for more than thirty days due to pending input or payment may be placed on hold.
  • Reactivation is subject to team availability and may incur a remobilisation fee.
  • We notify you in writing before any suspension takes effect.

Project Closure

Closure follows final delivery and acceptance.

  • A project closes on final delivery and written acceptance.
  • Handover includes assets, access and documentation as listed in the proposal.
  • Work requested after completion is treated as a new engagement.
Team reviewing a project delivery timeline on screen
Milestones · Approvals · Delivery

Remember

  • Written approvals via Email or WhatsApp
  • Delays automatically extend delivery timelines
  • 30+ days inactive projects may be placed on hold
  • Post-completion work is a new engagement
Guideline 03

Ownership, Support & Legal Information

The commercial and legal framework behind every engagement — written plainly, not buried in clauses.

  • Ownership of final approved deliverables transfers upon receipt of full and final payment.
  • Working files, internal frameworks, research and proprietary methodologies remain the property of Pixel Infinite AI unless expressly transferred in writing.
  • Both parties treat strategy documents, data and commercial information as confidential.
  • Information is shared internally only with team members delivering the engagement.
  • Pixel Infinite AI reserves the right to present completed work in its portfolio and marketing materials.
  • This right is waived in writing where confidentiality is required.
  • Hosting, domains, licences, plugins, APIs and media platforms are billed to and owned by the client.
  • We are not liable for outages, pricing changes or discontinuation of third-party services.
  • Where accounts are managed on your behalf, access is transferred at closure.
  • The post-launch support window is stated in the proposal and covers defects in delivered work.
  • New features, content changes and enhancements are covered by a maintenance agreement or quoted separately.
  • Support excludes issues caused by third-party changes or edits made by other parties.
  • Both parties commit to respectful, professional communication throughout the engagement.
  • We reserve the right to decline or discontinue work where conduct is abusive, unlawful or unethical.
  • Neither party solicits the other's personnel during the engagement or for six months thereafter.
  • Total liability is limited to the fees paid for the deliverable in question.
  • We are not liable for indirect or consequential loss, including loss of profit, revenue or data.
  • These terms are governed by the laws of India, with jurisdiction as stated in the proposal.

Acceptance

Approval of the proposal or payment of the advance amount constitutes acceptance of Pixel Infinite AI's Project Terms & Conditions.

Back to Home

Last updated: August 2026