Verity for gaming studios

You build worlds. Verity keeps the milestones, bugs and live events from slipping.

A game studio juggles a design that keeps changing, a build that has to pass store review, a publisher waiting on a milestone and players expecting new content on schedule. Each lives in a different tool. Verity ties them to each title so the team can see what blocks the next release.

Verity in one line

One system that follows each game from milestone plan to build, QA, release and live events, and shows what is late, who owes what and what the next payment depends on.

See your game studio in Verity See the 14 problems we solve

Free: we set up a working demo of your own business, on your own data, within 7 days. You pay only if your team decides to use it.

Built for a studio of five to a few hundred who already use a game engine and a bug tracker. Verity does not replace them. It joins what they know.

Verity / Studio / This week

All titles

Live

Titles

3

2 live, 1 in production

Milestones at risk

2

₹48 L tied up

Release blockers

9

bugs

Vendor items late

5

deliveries

Team load this week, by discipline

  • Engineering92%
  • Art118%
  • QA104%
  • Design76%

Milestone 3 for Publisher X is due in 9 days with 14 open features. ₹32 lakh depends on it.

Replan
  • Weekend event for Title 1Store items not ready, 3 days leftChase
  • Store data disclosure for Title 2Submission FridayAssign

Illustrative screen with sample figures. Yours is set up with your own titles, milestones, builds and vendors.

How it runs today

Most studios track bugs well and everything around them loosely.

The game has a design document, a task board and a build server. The business around it, meaning publisher milestones, vendor art, live event calendar, support and spend, sits in chats and spreadsheets.

The market is crowded. India has approximately 1,888 gaming companies employing more than 130,000 people, and most studios build for mobile stores that take a 30 percent commission, where being found without a paid budget takes luck.

Players expect more than a launch. Mobile audiences expect complex live-ops systems, a production load many indie studios cannot yet sustain, so a calendar of events and fixes matters as much as the first build.

What most game studios run on

  • Game engine and build server
  • Bug tracker or task board
  • Spreadsheet of milestones and vendor payments
  • Chat groups for art and QA
  • Analytics dashboards for each title

Each tool is good at one job. None shows whether the next publisher payment is at risk, which vendor is late or whether the live event can ship.

14 problems, one by one

Where a game studio loses time, money and players.

These are the situations studio founders and producers describe. For each one: what it looks like, what it costs, and what Verity does about it.

  1. 01Publishers

    Publisher milestones and payments drift

    What it looks like

    A publisher pays on milestones. The definition of "done" for milestone three is in an email from March. The build is delivered, the publisher asks for changes and payment waits.

    What it costs you

    Cash stuck for weeks, and a studio that pays salaries before the milestone money arrives.

    How Verity fixes it

    Each milestone records its deliverables, acceptance criteria, due date, the publisher's feedback and the payment tied to it. Verity shows which milestones are at risk and how much money depends on them.

    See the screen
  2. 02Production

    Scope grows and the design document is out of date

    What it looks like

    Features are added in meetings and chats. The design document describes a different game from the one in the build.

    What it costs you

    A schedule that slips with no clear cause and a team that argues about what was agreed.

    How Verity fixes it

    Each feature is a record with its description, owner, size and status. Changes need a recorded decision, and the milestone shows what has been added and removed.

    See the screen
  3. 03QA

    Builds and test passes are tracked in chats

    What it looks like

    Three builds went out this week. Testers do not know which one contains which fix, and a regression test is run on an old build.

    What it costs you

    Bugs reported twice, a bad build sent to a publisher and release days lost.

    How Verity fixes it

    Each build is a record with its version, contents, test results and who approved it. Testers see which fixes to verify, and a build cannot be marked ready without passing the checks you set.

    See the screen
  4. 04QA

    The bug list has no priority that people agree on

    What it looks like

    Two thousand open bugs. Nobody can say which five block the release or which can wait.

    What it costs you

    Engineers fixing minor issues while a crash that hits many players waits.

    How Verity fixes it

    Bugs carry severity, how many players or testers hit them and a release target. Verity shows release blockers and bugs by area and age.

    See the screen
  5. 05Vendors

    Art and audio vendors deliver late and in the wrong format

    What it looks like

    An outsourcing studio delivers 3D characters. Some miss the polygon budget and the lead artist asks for rework. Payment was promised on delivery.

    What it costs you

    Schedule slips, rework disputes and bills that do not match what was accepted.

    How Verity fixes it

    Each asset request has a brief, spec, due date and status through review. Verity lists deliveries late or rejected and compares bills with accepted work.

    See the screen
  6. 06Live ops

    Live events and content drops are missed

    What it looks like

    A weekend event needs new content, a store item and a notice. The item is not ready on Friday and the event goes out thin.

    What it costs you

    Players who see a poor event stop coming back. Mobile audiences expect complex live-ops systems, and a missed event is visible at once.

    How Verity fixes it

    Each event is a record with a date, its content, store items, tests and a sign-off. Verity lists events with open tasks and counts down to the day.

    See the screen
  7. 07Live ops

    Player support and bug reports are scattered

    What it looks like

    Players report issues in reviews, forums and support emails. A refund request and a crash report sit in the same inbox.

    What it costs you

    Slow replies, repeated reports of the same issue and no link between players' words and the bugs engineers fix.

    How Verity fixes it

    Player issues become tickets linked to known bugs. Verity shows how many reports each bug has and which players were promised a fix or a refund, and the team sends the replies.

    See the screen
  8. 08Money

    Monetisation numbers are read late

    What it looks like

    Revenue per paying user, retention and store fees sit in different dashboards. A pricing change is judged weeks later.

    What it costs you

    Decisions made on gut. With both big stores taking 30 percent and average revenue per paying user in non-real-money games at about USD 3, small changes matter.

    How Verity fixes it

    Key numbers for each title are recorded weekly beside releases and events, so a change can be read against what shipped. Detailed analytics stay in your tools.

    See the screen
  9. 09People

    Crunch is invisible until people leave

    What it looks like

    Before a milestone the team works late for three weeks. Nobody records the hours, and two people resign after launch.

    What it costs you

    Lost people in a market short of specialist skills, and a studio that repeats the pattern each milestone.

    How Verity fixes it

    Hours worked and load per person are recorded against tasks. Verity shows who is over capacity for how many weeks, so a producer can cut scope or move work before people burn out.

    See the screen
  10. 10Vendors

    Outsourced work and freelancers are paid from memory

    What it looks like

    Freelance artists and sound designers are paid per task. Some tasks were approved, some reworked, and the tracker disagrees with the chat.

    What it costs you

    Overpayment, delayed payment and unhappy freelancers.

    How Verity fixes it

    Each paid task shows its approval and the amount due. Verity lists approved work not yet paid and rework outstanding.

    See the screen
  11. 11Compliance

    Store rules, ratings and children's data

    What it looks like

    A store update asks for a new data disclosure. The game collects age and device data, and some players are children. Nobody owns the checklist.

    What it costs you

    A rejected build, a delayed release or a complaint about children's data. India's data protection rules were notified in November 2025, and most duties start to apply over the following 12 to 18 months.

    How Verity fixes it

    Store requirements, age ratings and data disclosures are a checklist with owners and dates for each title. Verity shows what is open before a submission.

    See the screen
  12. 12Publishers

    Publisher recoupment and revenue share are hard to follow

    What it looks like

    A publisher advances money against future revenue. Revenue statements arrive monthly and nobody checks that deductions are right.

    What it costs you

    Money lost in deductions you never questioned, and surprise when recoupment is slower than expected.

    How Verity fixes it

    Each publisher deal records the advance, share, deductions allowed and statements received. Verity compares statements with the terms and lists items to query.

    See the screen
  13. 13Money

    User acquisition spend is not tied to results

    What it looks like

    A campaign spends ₹3 lakh in a week. Installs come in, but nobody joins the spend to the players who stayed.

    What it costs you

    Budgets burnt on channels that bring players who never return. Without paid acquisition, discovery on the stores is hard, so spend matters.

    How Verity fixes it

    Each campaign records spend, dates and the result figures you enter. Verity shows cost per install and per retained player by channel and title.

    See the screen
  14. 14Owner

    The founders carry every title in their heads

    What it looks like

    With two live games and one in development, the founders remember which release is blocked, which milestone is due and which vendor is slow.

    What it costs you

    A studio that cannot add a third title or a second team without losing context.

    How Verity fixes it

    Each morning Verity shows what needs a decision across titles, each item with an owner. A second team or studio becomes a location in the same system.

    See the screen

The numbers behind it

The numbers that make these problems worth fixing.

From published sources, with the source named under each figure. Your own numbers will differ, and showing you yours is the first thing Verity does.

  • 1,888

    gaming companies in India employing more than 130,000 people, according to the India Gaming Report 2025 as cited in Business Today.

    Business Today, 2026

  • 30%

    the commission both major app stores take on every transaction, in a market where average revenue per paying user in non-real-money games is about USD 3.

    Business Today, 2026

  • USD 1.04 billion

    India's gaming market revenue in 2025 excluding real-money games, up 14.8 percent with 511 million players.

    Niko Partners, 2026

  • Up to ₹1 crore

    the fine, with up to three years' imprisonment, for offering online money games under the Promotion and Regulation of Online Gaming Act 2025. Social games without monetary stakes and qualifying e-sports are permitted.

    Mondaq, 2025

Market size figures differ widely between sources because they count different things, so the page uses the narrowest reputable one. The studio count comes from an advertorial-style feature citing an industry report. The Online Gaming Act summary comes from a law-firm article, and the commencement date was reported differently elsewhere.

What you will actually see

The screens you would use every day.

Seven views, each for one job. Titles, milestones, builds and vendors are set up in your own terms.

Screen 1 of 7

The studio head's weekly view

Milestones at risk, release blockers, live events coming, vendor deliveries and cash tied to publishers on one screen, with the items that need a decision listed below.

Fixes

  • 08 Monetisation numbers are read late
  • 14 The founders carry every title in their heads

Verity / Studio / This week

All titles

Titles

3

2 live, 1 in production

Milestones at risk

2

₹48 L tied up

Release blockers

9

bugs

Vendor items late

5

deliveries

Team load this week, by discipline

  • Engineering92%
  • Art118%
  • QA104%
  • Design76%

Milestone 3 for Publisher X is due in 9 days with 14 open features. ₹32 lakh depends on it.

Replan
  • Weekend event for Title 1Store items not ready, 3 days leftChase
  • Store data disclosure for Title 2Submission FridayAssign

Screen 2 of 7

Features, milestones and capacity

Features with owner, size and status against each milestone, with additions and removals recorded and team load shown week by week.

Fixes

  • 02 Scope grows and the design document is out of date
  • 09 Crunch is invisible until people leave

Verity / Production

Title 3

To do2

  • Daily rewards systemAdded 2 Oct, decision recordedAdded
  • Tutorial reworkSize 8 days, unownedAssign

In progress2

  • Boss fight 2Anil, day 6 of 10On track
  • Inventory screenPriya, 2 days overSlipping

Done for milestone 31

  • Level 4 layoutAccepted by the publisherDone

Screen 3 of 7

Builds and bugs

Each build with its contents and test results, and the bugs that block the next release, ordered by severity and number of players or testers affected.

Fixes

  • 03 Builds and test passes are tracked in chats
  • 04 The bug list has no priority that people agree on

Verity / QA

Last 5 builds

BuildContentsTestsApprovedStatus
0.9.14Fixes 41 bugsPassedLead QASent to publisher
0.9.15Boss fight 22 failuresNoneHold
0.9.16Inventory UINot runNoneTest
BugSeverityPlayers hitTargetStatus
Crash on level 4 loadBlocker4200.9.16Open
Save data lossBlocker380.9.16In progress
Menu text overlapMinor2After launchBacklog

Screen 4 of 7

Events, content drops and player reports

The events calendar with content, store items, tests and sign-off for each, and player reports linked to the bugs they relate to.

Fixes

  • 06 Live events and content drops are missed
  • 07 Player support and bug reports are scattered

Verity / Live ops

Next 4 weeks

EventDateContentStore itemsStatus
Weekend event, Title 118 OctReadyNot readyChase
Festival pack, Title 11 NovHalf donePlannedOn track
Season update, Title 28 NovNot startedNot startedAt risk
  • Crash on level 4 load112 player reports, 38 reviewsReply
  • Refund requests, 14Promised a fix by 20 OctOwed

Screen 5 of 7

Milestones, payments and revenue statements

Each publisher deal with milestones, acceptance, payments tied to them and the monthly revenue statements checked against the agreed terms.

Fixes

  • 01 Publisher milestones and payments drift
  • 12 Publisher recoupment and revenue share are hard to follow

Verity / Publishers

Deals and milestones

MilestoneDuePaymentPublisher feedbackStatus
M2, vertical slice20 Sep₹16 LAcceptedPaid
M3, alpha27 Oct₹32 LChanges askedAt risk
M4, beta15 Dec₹40 LNot startedPlanned

September revenue statement from Publisher X deducts ₹1.4 lakh in costs not listed in the agreement.

Query

Screen 6 of 7

Outsourcing, freelancers and campaign spend

Assets requested from vendors and freelancers with due dates, review and amounts due, and campaign spend against the players it brought in.

Fixes

  • 05 Art and audio vendors deliver late and in the wrong format
  • 10 Outsourced work and freelancers are paid from memory
  • 13 User acquisition spend is not tied to results

Verity / Vendors and spend

Deliveries and campaigns

ItemVendorDueReviewStatus
12 enemy modelsStudio Alpha10 OctOver polygon budgetRework
Boss musicFreelancer18 OctNot yetDue
UI icon setStudio Beta5 OctAcceptedPay ₹60,000
CampaignSpendInstallsCost per installRetained at day 7
Channel A₹1.2 L4,100₹2912%
Channel B₹1.8 L6,300₹294%

Screen 7 of 7

Store rules, ratings and data duties

Store requirements, age ratings and data disclosures for each title as a checklist with owners and dates, so nothing is found at submission.

Fixes

  • 11 Store rules, ratings and children's data

Verity / Compliance

By title

  • Store data disclosure for Title 2Due Friday, Karan
  • Age rating answers reviewedDone 3 Oct
  • Ad partner data terms checkedDue 25 Oct, Ritu
  • Children's data approach documentedDone 1 Oct

Title 2 collects age and device data. The privacy notice is two versions behind the game.

Update

Illustrative screens with sample data. Layouts, fields, names and terms are set up around how your game studio works.

An ordinary day

The same Thursday, before and after.

The studio works the same way. What changes is that every promise leaves a record that chases for you.

WhenTodayWith Verity
10:00 TodayThe producer asks in chat which bugs block the build. With VerityThe release blockers list is on screen with owners and a target build.
11:30 TodayA publisher asks if milestone three is on track. The answer is a guess. With VerityFeatures done, features open and the money tied to the milestone are shown.
1:00 TodayA vendor delivers assets that miss the specification. Nobody notices for two days. With VerityThe delivery is flagged as late or rejected the day it arrives.
3:30 TodayThe weekend event has no store items. With VerityThe countdown warned on Monday that two items were open.
6:00 TodayA tester verifies a fix on the wrong build. With VerityThe build record says which fixes it contains.
Month end TodaySomeone reconciles vendor bills and the publisher statement from chats. With VerityAccepted work, payments due and the statement terms are on one list.

How we work with you

We set it up with you, in four weeks.

You do not get a login and a manual. We learn how your titles actually get made and run, build Verity around that, bring your data in, then stay on to keep it working.

  1. Week 1

    Discovery and mapping

    What we do
    Spend a day with your producer, a lead engineer, a QA lead and whoever pays vendors. Follow a feature from design to release, and map your tools for tasks, bugs, builds and money.
    What we need from you
    A few hours from you and your producer. Your current milestone plan, bug tracker export and publisher agreement summaries.
    What you have at the end
    A written map of how production, QA, live ops, vendors and money run today and the problems to fix first.

  2. Weeks 2 to 3

    Configuration

    What we do
    Set up titles and milestones, feature and bug records with severities, build records and checks, event calendar, vendor requests, publisher deals and statements, compliance checklists and approvals.
    What we need from you
    Check the severities, build checks and milestone definitions with your producer and QA lead.
    What you have at the end
    A working Verity with your real titles, milestones and rules.

  3. Weeks 3 to 4

    Migration and training

    What we do
    Bring in open features, milestones, vendors and their open requests, events and publisher deals. Train producers, leads and the finance owner on a live milestone.
    What we need from you
    Your milestone list and open vendor items, in whatever form they exist. One hour per role.
    What you have at the end
    Your studio inside Verity and a team that has used it on a real milestone.

  4. After go-live

    Operations partnership

    What we do
    Stay on after launch. Review the first weeks with you, tune lists and reminders and handle new titles, teams and publishers.
    What we need from you
    A short monthly review of what the numbers say.
    What you have at the end
    A system that keeps matching how the studio runs, with someone responsible for it.

Bring these on day one

  • Your milestone plan for each title
  • Current bug list export
  • Vendor and freelancer list with open requests
  • Publisher agreements and statements
  • Your live events plan

Your time

About 7 to 10 hours of owner time across the four weeks, mostly in week 1. Your producer and QA lead need a few more.

After go-live

Nobody is hired to run Verity. Milestones, builds and requests are recorded as part of the work you already do, and the reports come from those records.

Verity AI

Ask your studio a question.

Verity AI reads your milestones, features, bugs, events, vendors and publisher deals. Ask in plain language, then turn the answer into tasks for the right person.

  • Your records only Answers come from your own game studios data, not from generic knowledge.
  • Right person, right view It only shows what the person asking is allowed to see.
  • Turns into action An answer can become a task assigned to a named person.

Verity / Ask

Which milestones are at risk and how much money depends on them?

Milestone 3 for Publisher X is at risk, with 14 open features and ₹32 lakh tied to it.

  • Milestone 3₹32 L
  • Milestone 2 for Publisher Y₹16 L

Create a replanning task for the producer

Verity / Ask

Which bugs block the next release and how many players are hit?

Nine blockers. The crash on level 4 load has hit 420 players and the save data loss 38.

  • Crash on level 4 load420 players
  • Save data loss38 players

Assign the blockers to the engineering lead

Verity / Ask

Which vendor deliveries are late or rejected?

Five. Studio Alpha's 12 enemy models are over the polygon budget and the boss music is due 18 October.

  • Studio Alpha12 models
  • Freelancerboss music

Create chase tasks for the art lead

Sample questions and answers with illustrative figures.

Without chasing

The follow-ups nobody has time to make.

Set once, then they run from your records. People still make and ship the game. Verity makes sure the right person knows to.

When

A milestone is 14 days from due with more than 20 percent of features open

  • Flagged to the producer
  • Money tied to it shown
  • Replan decision recorded

When

A build is created

  • Contents and fixes listed for testers
  • Test checks assigned
  • Marked ready only after checks pass

When

A bug blocks the next release and is untouched for 3 days

  • Flagged to the engineering lead
  • Reassigned if needed
  • Status recorded

When

An event is 7 days away with content or store items open

  • Flagged to the live ops owner
  • Open items listed
  • Sign-off recorded or the event moved

When

A vendor delivery is late or rejected

  • Task to the art or audio lead
  • Rework request recorded
  • Payment held until accepted

When

A store requirement or disclosure is due before a submission

  • Task to its owner
  • Documents attached
  • Completion recorded

Rules and paperwork

The rules a gaming studio has to keep up with.

Verity does not give legal advice and does not file anything for you. It keeps the records these rules and your publishers' contracts depend on in order.

  • Online money games and what is permitted

    What is expected

    The Promotion and Regulation of Online Gaming Act 2025 prohibits online money games, whether of skill or chance, and sets no licensing route. Online social games without monetary stakes and qualifying e-sports are permitted. The date it took effect was reported differently by different sources, so confirm it.

    How Verity helps

    Each title records its game type and monetisation, so you can show that real-money features are not offered.

    Mondaq

  • Store rules and commission

    What is expected

    Both major app stores take a 30 percent commission and set their own rules on data disclosure, age ratings and content. A build can be rejected for missing items.

    How Verity helps

    Store requirements are a checklist per title with owners and dates, and submissions record what was declared.

    Business Today

  • Players' personal data, including children

    What is expected

    India's data protection rules were notified in November 2025, and most duties start to apply over the following 12 to 18 months. Games with child players may need extra care and parental consent.

    How Verity helps

    Data collected by each title, notices and consent records are listed with owners, and access to player data is by role.

    AZB Partners

  • Publisher, vendor and freelancer contracts

    What is expected

    Publisher deals set milestones, advances and revenue shares, and vendor contracts set specifications and acceptance. Rights to the work depend on what the contract says.

    How Verity helps

    Terms sit on each deal and vendor record and are compared with deliveries, statements and payments.

Rules and store requirements change often and differ by title and market. Confirm current requirements with your lawyer and the store's own documents.

Who sees what

Everyone sees the same records, through their own window.

A freelancer should not see publisher terms. Engineers should not see salaries. Each role opens on what it needs.

  • Studio head

    Which titles and deals need my attention?

    Milestones at risk, money tied to publishers, release blockers, events coming and spend.

  • Producer

    What is the plan and what slipped?

    Features by milestone, team load, vendor deliveries, decisions and risks.

  • QA lead

    What is in each build and what is left?

    Builds and test results, bug counts by severity, blockers and verification tasks.

  • Live ops owner

    What ships next and what do players say?

    Event calendar, content and store item status, player reports linked to bugs.

  • Finance owner

    What is due and what is owed?

    Milestone payments, vendor and freelancer dues, campaign spend and revenue statements.

Straight answers

What changes, and what stays the same.

Keep using

  • Your game engine, build server and version control
  • Your bug tracker if you like it
  • Your analytics and store consoles
  • Your accountant, who still prepares your returns

Verity does not

  • Build, host or publish your games
  • Run store submissions or player payments
  • Send messages to players or publishers on its own
  • Give legal or tax advice

We bring your milestone plans, open features and bugs, vendor items and publisher deals across from the sheets, trackers and chats you use now, in stages, so production keeps moving while it happens.

  • Excel
  • Google Sheets
  • Legacy ERP
  • CRM
  • One operating environment

Questions

Questions game studio owners ask.

We already use a bug tracker and a task board. Why add this?

Keep them. Verity does not replace them. It joins them to the business around the game: milestones and payments, vendors, live events, spend and compliance. We agree during setup what stays in your tools.

Will artists and engineers use it?

It only works if recording takes seconds, so we set it up around the boards they already use. They get a clear view of their week, the feature or asset spec and what the milestone depends on.

Can it track bugs well enough to replace my tracker?

It holds bugs, severity and status and links them to builds and player reports. If you prefer a specialist tracker, we agree how status reaches Verity so everything is in one view.

Does it handle live ops?

Yes. Events are records with content, store items, tests and sign-off, and a calendar. Verity does not run the live game or send notices to players.

Can it help with publisher payments?

Yes. Milestones, acceptance, payments and revenue statements are on one view, with deductions compared with the agreed terms. It does not make or receive payments.

We outsource a lot. Can it manage vendors?

Yes. Each request has a spec, due date, review and payment due, and late or rejected items are listed.

Who can see what?

Only the people you allow. Access is set by role and by title, and every change is recorded with who made it and when.

How long before I see results?

The release blockers list, milestone risk view and vendor delivery list need only your existing records, so they are the first things we aim to have working. Spend and live ops trends need a few weeks of use.

What does it cost?

It depends on the number of users and what you want set up. Message us and we will give you a clear number after a short conversation about how your studio runs.

Where the figures come from

Sources

  1. Business Today, 16 Jul 2026
  2. Niko Partners, 2026
  3. Mondaq
  4. AZB Partners on the DPDP framework

Last checked 16 October 2026. Published figures vary by region and method, so treat them as indicative, not as a promise of your results.

See which milestone is really at risk.

Tell us how your studio runs and we will show you the release blockers, late vendor items and events at risk it would find, using your own numbers.

Get your free demo Email us

Free: we set up a working demo of your own business, on your own data, within 7 days. You pay only if your team decides to use it.