How to Choose a Branded AR Filter Vendor for a Corporate Campaign

Start with the campaign job, not the effect

Selecting a vendor for a corporate campaign branded AR filter in Singapore requires more than reviewing attractive mock-ups. The buyer must determine whether each supplier understands the campaign objective, the intended audience journey and the operational work needed to move from concept to launch.

Define what the filter is meant to achieve. It might encourage participation at an event, support a product announcement, extend a brand activation into social sharing or add an interactive layer to a staff campaign. These are different assignments. They affect the creative treatment, interaction length, production schedule, publishing route and support required.

Your brief should identify the audience, campaign dates, intended channels, brand rules, languages, markets, approval stakeholders and expected user action. If the activation sits within a wider event, explain where people will discover it and who will help them participate. For more help shaping the project itself, see the corporate AR filter requirements guide.

Issue the same information to every shortlisted vendor

Proposal comparison becomes unreliable when suppliers respond to different assumptions. Prepare one controlled brief and record all clarifications in a shared question log. Vendors should know whether they are pricing a defined concept, proposing concepts from scratch or advising on feasibility before the creative direction is fixed.

Include these procurement inputs

• Campaign context: objective, audience, location, dates and relationship to other campaign activity.
• Experience outline: intended interaction, visual references, sharing journey and any required physical touchpoints.
• Brand materials: current logos, fonts, colour guidance, campaign artwork and approval rules.
• Technical context: target platform, supported devices where relevant, account ownership and publishing constraints.
• Governance: reviewers, decision maker, feedback method, revision windows and final approval authority.
• Delivery expectations: demonstrations, test builds, documentation, launch support and post-launch assistance.

A vendor may need discovery before confirming the final solution. That is reasonable when platform rules, assets or interaction complexity remain unresolved. Ask the supplier to separate confirmed scope from assumptions, options and items requiring validation.

Compare proposals line by line

A useful proposal makes responsibility visible. It should explain what the supplier will create, what the buyer must provide and which external approvals or platform processes could affect delivery. Avoid comparing only the total fee. Two proposals with similar creative descriptions may cover very different amounts of concept development, testing, revisions and launch support.

Questions for each proposal

1. How many concepts are included, and what level of visual development accompanies each one?
2. What interactive behaviours, animation, audio or game logic are included?
3. Which target platform and publishing method does the proposal assume?
4. Who prepares, adapts and approves brand assets?
5. What testing is included, and which devices or operating conditions will be sampled?
6. How many review rounds are included at each stage?
7. What documentation, handover material and launch support will be supplied?
8. Which costs or services are expressly excluded?

Request an itemised change process. A useful change mechanism states how a new request will be assessed for cost, schedule and technical consequences before work proceeds. This protects both parties when campaign requirements evolve after concept approval.

Use demonstrations to test thinking and execution

A demonstration should reveal more than presentation skills. Give shortlisted vendors a realistic scenario and ask them to explain the proposed user journey, likely constraints and production sequence. They do not need to produce unpaid finished creative. A storyboard, interaction map or limited prototype can be enough to expose whether their decisions are grounded in the brief.

Observe how the team handles failure cases. Ask what happens when recognition conditions are poor, a device behaves differently, connectivity is limited or a platform requirement changes. Outcomes depend on the chosen tools, platform support and agreed test coverage, so a credible supplier should describe dependencies rather than promise universal performance.

Ask who will attend working sessions after appointment. The people delivering the project should be able to discuss creative, production and campaign operations without every question passing through a sales layer.

Set responsibility boundaries before appointment

Record ownership for every dependency. The buyer may provide approved artwork, trademarks, campaign copy, account access and timely feedback. The vendor may be responsible for concept development, production, testing coordination and deployment assistance within the agreed scope. If another agency controls media, social accounts, event production or campaign creative, define how the teams will exchange assets and decisions.

Get Out! Events can scope branded AR filter work through GO Labs and coordinate it with wider corporate event delivery where required. The precise production, platform and support responsibilities should still be documented for each engagement. Buyers seeking broader context can review the corporate campaign branded AR filter overview.

Make exclusions explicit

Common areas requiring clarification include media spend, influencer activity, device provision, venue connectivity, third-party licences, platform fees, photography, video production, translation, moderation and extended support. Inclusion depends on the proposal. Do not assume that a creative production fee covers these adjacent services.

Define acceptance as observable checks

Replace vague requirements such as “works smoothly” with checks tied to the agreed experience. Acceptance criteria could cover approved visual assets, required interaction steps, copy accuracy, specified links, agreed test scenarios and delivery of handover materials. Technical checks should identify the target environment and reasonable test coverage rather than imply compatibility with every device.

Plan approval gates for concept, storyboard, prototype, test build and release candidate. State who can approve each gate and how consolidated feedback will be delivered. Also specify the response if a release candidate does not meet an agreed criterion: correction, retest, documented exception or an approved scope change.

Review privacy and platform dependencies carefully

Ask what information the proposed experience processes, whether any data is collected and which parties control relevant accounts or systems. Requirements vary by design and platform. Privacy, consent, retention and notice questions should be reviewed against the actual implementation and your organisation’s policies, with appropriate professional advice where needed.

Platform availability, review processes and feature support can change. The contract and launch plan should distinguish supplier-controlled work from third-party decisions. Include contingency discussions early, especially when campaign dates cannot move.

Choose the team that reduces delivery ambiguity

Score suppliers against weighted criteria agreed before proposals arrive. Useful categories include understanding of the brief, creative relevance, technical approach, production plan, testing, responsibility clarity, team capability, commercial transparency and risk handling. Keep presentation quality separate from delivery evidence.

The preferred vendor should make the project easier to govern. Look for specific assumptions, direct answers, disciplined exclusions and a realistic approval path. A compelling idea matters, but corporate campaign delivery also depends on clear ownership and controlled decisions. Select the proposal that gives stakeholders confidence about what will be produced, how it will be evaluated and who acts when conditions change.