Verity for app development companies

The build is done. The store has it in review, and your client thinks it is live.

An app studio delivers through gates it does not control, and gets judged after release. Store review, platform deadlines, client sign-off and post-release bugs decide whether a project makes money. Verity keeps all of them against the app and the client.

Verity in one line

One system that knows every app you built, which version is live, who owns the store account, what the client asked for and what you have not yet billed.

See your app development company 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.

Your code, build tools and store consoles stay where they are. Verity runs the company around them.

Verity / Studio / Today

All clients, this month

Live

Apps maintained

31

18 clients

Releases in review

4

1 rejected

Retainer hours over

58

across 6 clients

Invoices unpaid

₹14.2 L

₹6.1 L past 45 days

Estimated against actual hours, finished projects

  • Food ordering app+66%
  • Fitness tracker+24%
  • Booking app+8%
  • Internal sales app-4%

Two apps will fall below the Google Play target level within 90 days.

Quote upgrade
  • Wellbeing app rejected by AppleMissing privacy detailTell client
  • Aarav Logistics retainer at 92%19 of 20 hours, 11 days leftCall

Illustrative screen with sample figures. Yours is set up with your own apps, clients, developers and retainers.

How it runs today

The code is well managed. The company around it is not.

Developers live in the repository, the task board and the chat. That part is organised. What sits outside is not: which client approved which change, which app is waiting in store review, who holds the signing key for a client’s Android app, and how many support hours were spent on a project that was sold as fixed price.

That information is spread over email threads, WhatsApp groups with clients, a task board per project, an accounts sheet and the founder’s memory. Nobody can open one client and see the apps, versions, open bugs, hours, invoices and agreements together.

So the studio finds out late. A store rejection that costs a week. A platform deadline noticed after the notice period. A maintenance client who used 40 hours against 20 paid. A developer who leaves with the only copy of a certificate.

What most app development companies run on

  • Task board per project
  • Git hosting and build tools
  • Client WhatsApp groups
  • Time and invoice sheets
  • Founder’s memory

Each of these does its job well. Nothing joins the app, the client, the time and the money.

14 problems, one by one

Where an app studio actually loses money.

These are the situations studio owners describe again and again. For each one: how it looks, what it costs, and what Verity does about it.

  1. 01Release

    Store review takes a week and nobody told the client

    What it looks like

    The build was done on Friday. Apple rejected it Monday for a missing privacy detail. The client was told the app would be live by Tuesday and has already announced a launch date.

    What it costs you

    Apple rejected over 1.9 million of 7.7 million submissions in 2024. Each rejection typically costs you days of rework and a difficult call, and the launch date is already public.

    How Verity fixes it

    Every release is a record with a state: built, submitted, in review, rejected with reason, approved, live. Rejections create a fix task with the reason, and the client’s account manager sees the status so the message is sent before the client asks.

    See the screen
  2. 02Release

    Platform deadlines arrive as emails nobody reads

    What it looks like

    From 31 August 2026, new apps and updates on Google Play must target Android 16 (API 36). A client’s app is built for an older level and nobody knew until an update was blocked.

    What it costs you

    An update held up by a rule you could have planned for, and apps that become unavailable to new users on newer devices. Extensions can be requested, but only if someone asks in time.

    How Verity fixes it

    Each app record holds its target platform version and the dates platforms have announced. A list shows apps that will fall out of compliance within 90 days, with an upgrade task and a quote for the client.

    See the screen
  3. 03Scope

    Small changes agreed on calls add up to a lost project

    What it looks like

    In week five the client asks on a call for "a quick filter and a second payment option". It is agreed to keep the relationship warm. By week nine there are eleven such changes and none were priced.

    What it costs you

    Example arithmetic: eleven changes at 12 hours each is 132 hours. At ₹1,500 an hour, that is ₹1.98 lakh of work given away on a ₹9 lakh project.

    How Verity fixes it

    Every request is logged as a change request on the project with hours, price and a status: asked, estimated, approved, declined, delivered. Approved changes add to the project value, and unpriced work is visible as a count.

    See the screen
  4. 04Scope

    The client takes two weeks to answer and the delay is still your problem

    What it looks like

    Designs wait for sign-off for ten days. The sprint stalls. When the launch date slips, the client says development was late.

    What it costs you

    Developers idle or switched to other work, and a fight over whose delay it was. Without dates you cannot show the client’s part.

    How Verity fixes it

    Each approval is a task assigned to a named person at the client, with a due date and a reminder for your team to chase. When the project slips, the record shows days spent waiting on the client.

    See the screen
  5. 05Quality

    Bugs after release arrive through every channel except the one you track

    What it looks like

    The client sends a screenshot on WhatsApp on Sunday. The developer hears about it Monday afternoon. Twenty-three bugs in the first 48 hours appear as scattered messages.

    What it costs you

    You cannot tell whether the release was weak or the client was just thorough. A fix goes out without the client knowing which bugs it covered.

    How Verity fixes it

    Every report becomes a defect on the release, with severity, owner, and the build it was found in and fixed in. You see defects per release and per client, and whether the first 48 hours are getting better.

    See the screen
  6. 06Quality

    A new iOS or Android version breaks an app you shipped a year ago

    What it looks like

    The new operating system arrives in September. Four apps you built crash on the new version. Clients without a maintenance contract write to you angrily.

    What it costs you

    Unplanned work for clients who never agreed to pay for it, or reputation damage if you refuse.

    How Verity fixes it

    Every app records its client’s support terms. When a platform release lands, you see which apps are affected, which are under a retainer and which are not, and a quote task goes out for those that are not.

    See the screen
  7. 07Support

    Maintenance retainers use more hours than clients pay for

    What it looks like

    A client pays for 20 hours a month. Last month the team spent 41 on small requests. Nobody counted because each one was only a message.

    What it costs you

    Example arithmetic: 21 extra hours at ₹1,500 across 10 retainer clients is ₹3.15 lakh a month of free work.

    How Verity fixes it

    Each retainer has its monthly hours. Time is logged against it, and the screen shows hours used and the pace for the month. At 80 percent a task goes to the account manager to talk to the client.

    See the screen
  8. 08Money

    Milestone invoices go out late and are paid later

    What it looks like

    The beta milestone was reached on the 10th. The invoice went out on the 26th because the founder was busy. The client pays 45 days after that.

    What it costs you

    Working capital funds the client’s project. Salaries are paid on the 1st whether or not the milestone cash has arrived.

    How Verity fixes it

    Each milestone is a record tied to the project. When it is marked done, an invoice task goes to finance with the amount. Invoices not yet paid are listed by client and age, with a follow-up task for each.

    See the screen
  9. 09Estimating

    Quotes are based on memory, not on what similar apps took

    What it looks like

    A new prospect wants a food-ordering app. Someone says "about three months". Last time it took five, but the hours were never added up.

    What it costs you

    Quotes that lose money when they win and lose the deal when they are padded.

    How Verity fixes it

    Every finished project keeps estimated against actual hours by feature type. The owner view compares them, so the next quote is built on what the studio really takes.

    See the screen
  10. 10People

    Developers are double booked, or sitting between projects

    What it looks like

    Two projects both need your best Flutter developer in the same fortnight. A third developer has been idle for ten days because nobody saw a project end.

    What it costs you

    A delayed launch on one side and unbilled salary on the other. Bench cost in a studio is easy to hide inside the month’s total.

    How Verity fixes it

    Assignments by person and week are in one schedule, with leave. Over-booking and idle weeks are flagged early, and utilisation per developer is a live number.

    See the screen
  11. 11People

    When a developer leaves, the knowledge leaves too

    What it looks like

    Only one engineer knew how the release for a fintech client is signed and uploaded. She resigns with a two-week notice.

    What it costs you

    Release delays, a rushed handover and a risk that the client’s app cannot be updated.

    How Verity fixes it

    Each app record lists who knows it, how releases are made, and what has been handed over. A handover checklist starts the day a resignation is recorded.

    See the screen
  12. 12Accounts

    Nobody is sure who owns the store account, the keys or the renewals

    What it looks like

    Some apps are published from the client’s developer account, others from yours. Signing keys sit on a laptop. The yearly developer fee lapses and the app disappears.

    What it costs you

    An app removed from the store over a missed renewal, or a dispute about who owns the account when the contract ends.

    How Verity fixes it

    Each app lists its store accounts, owner, key location, third-party services and renewal dates. Renewals appear on a list 60 days ahead with a task to the account manager.

    See the screen
  13. 13Clients

    Every client message lives in a separate chat

    What it looks like

    The client’s product manager, founder and designer all message different developers. A decision made in one chat is unknown in another.

    What it costs you

    Rework from contradicting instructions and no written trail when a dispute arrives.

    How Verity fixes it

    Decisions, approvals and requests are recorded on the project with who gave them and when. The chat stays for talking, but the decision is written against the project.

    See the screen
  14. 14Compliance

    Apps collect personal data and the contract does not say who is responsible

    What it looks like

    A health app stores names, phone numbers and reports. The client assumes you handle compliance. Your contract is silent on data handling, breach and deletion.

    What it costs you

    A dispute the day a breach happens, and extra work when the data protection duties begin to apply.

    How Verity fixes it

    Each app record lists the personal data it collects, where it is stored, who can access it and the agreement that covers it. Gaps appear as tasks before the new duties start.

    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.9 million

    of over 7.7 million app submissions to the App Store were rejected in 2024 for not meeting its standards.

    Apple Newsroom, 2025

  • 31 Aug 2026

    date from which new apps and updates on Google Play must target Android 16 (API level 36). Extensions could be requested until 1 November 2026.

    Android Developers, 2026

  • 13 May 2027

    date from which the main duties of India’s data protection rules, including notice, consent and safeguards, are due to apply, after the rules were notified on 13 November 2025.

    AZB Partners, 2025

  • 45 days

    is the longest time a buyer should generally take to pay a micro or small supplier under the MSMED Act, or the buyer loses the tax deduction until it pays. It matters if your studio is registered as a micro or small enterprise.

    TaxGuru on Section 43B(h), 2024

Platform dates change often and are set by Apple and Google, so check each console. The 45-day rule applies only to micro and small suppliers with Udyam registration and has some exceptions, so ask your accountant. None of these show what your studio will see.

What you will actually see

The screens you would use every day.

Seven views, each built for one job. Apps, releases and retainers are set up in your studio’s own words.

Screen 1 of 7

The founder’s overview

Releases in flight, defects, retainer hours, unpaid invoices and how your estimates compare to what projects really took.

Fixes

  • 09 Quotes are based on memory, not on what similar apps took

Verity / Studio / Today

All clients, this month

Apps maintained

31

18 clients

Releases in review

4

1 rejected

Retainer hours over

58

across 6 clients

Invoices unpaid

₹14.2 L

₹6.1 L past 45 days

Estimated against actual hours, finished projects

  • Food ordering app+66%
  • Fitness tracker+24%
  • Booking app+8%
  • Internal sales app-4%

Two apps will fall below the Google Play target level within 90 days.

Quote upgrade
  • Wellbeing app rejected by AppleMissing privacy detailTell client
  • Aarav Logistics retainer at 92%19 of 20 hours, 11 days leftCall

Screen 2 of 7

Where every build is, and what the client has been told

Each release with its platform, state, review outcome and the date promised to the client, so rejections are handled before they become a call.

Fixes

  • 01 Store review takes a week and nobody told the client

Verity / Releases

Store review status

App, versionPlatformStatePromisedClient told
Wellbeing 2.4iOSRejected14 OctNo
Wellbeing 2.4AndroidApproved14 OctYes
Aarav Logistics 5.1AndroidIn review16 OctYes
FoodKart 3.0iOSBuilt20 OctNot yet

Wellbeing 2.4 for iOS was rejected: privacy detail missing. The fix is assigned to Rohan.

Open

Screen 3 of 7

Every bug report on the release it came from

Bug reports from clients, however they arrive, tied to the version, the severity and who is fixing it, and platform changes listed against the apps they affect.

Fixes

  • 05 Bugs after release arrive through every channel except the one you track
  • 06 A new iOS or Android version breaks an app you shipped a year ago

Verity / Defects and support

After release

ReportApp, versionSeverityOwnerState
Payment screen crashFoodKart 3.0HighIshanFix in build
Filter not savingWellbeing 2.4MediumRohanOpen
Push not arrivingAarav 5.1HighIshanOpen
Wrong logo on splashBooking 1.7LowMeeraFixed
  • New iOS version released4 apps affected, 1 under retainerQuote 3

Screen 4 of 7

Every ask priced, approved and written down

Change requests with hours and price, and approvals waiting on the client with a date. Decisions are recorded against the project, not left in a chat.

Fixes

  • 03 Small changes agreed on calls add up to a lost project
  • 04 The client takes two weeks to answer and the delay is still your problem
  • 13 Every client message lives in a separate chat

Verity / Projects and changes

Change requests

Asked, not priced2

  • Second payment optionFoodKart, asked on call 3 OctEstimate
  • Filter by cuisineFoodKart, 8 hoursEstimate

Waiting on client1

  • Sign off on checkout designPriya at FoodKart, 9 daysChase

Approved1

  • Order history export₹42,000, 28 hoursApproved

Screen 5 of 7

Hours used against hours paid, and invoices against age

Each maintenance client’s hours for the month, milestone invoices raised and still unpaid, and the follow-up for each.

Fixes

  • 07 Maintenance retainers use more hours than clients pay for
  • 08 Milestone invoices go out late and are paid later

Verity / Retainers and invoices

Hours and money

ClientHours paidUsedInvoice dueStatus
Aarav Logistics2019₹0.9 L92%
FoodKart3041₹2.1 L137%
Wellbeing Co159₹0.7 L60%
Booking Hub1012₹0.4 L120%

Beta milestone for FoodKart was met 12 days ago. Invoice not raised.

Raise invoice

Screen 6 of 7

Who is on what, and who knows what

Assignments by week, leave, bench time and a record of who can do releases for each app.

Fixes

  • 10 Developers are double booked, or sitting between projects
  • 11 When a developer leaves, the knowledge leaves too

Verity / Team

Next 4 weeks

DeveloperSkillThis weekNext weekNote
IshanFlutter120%100%Double booked
RohaniOS90%80%OK
MeeraAndroid20%0%Free from 22 Oct
TanviQA85%90%OK
  • Release keys handed over for Aarav LogisticsIshan leaves 30 Oct
  • Store accounts listedIshan
  • Build steps written downIshan

Screen 7 of 7

One record for every app you built

Platforms and versions, who owns the store account and keys, renewals, the data the app collects, and the contract that covers it.

Fixes

  • 02 Platform deadlines arrive as emails nobody reads
  • 12 Nobody is sure who owns the store account, the keys or the renewals
  • 14 Apps collect personal data and the contract does not say who is responsible

Verity / App

Record

Aarav Logistics driver app

Android and iOS. Client since 2024. Account manager: Pooja

Live version
5.0 (Android), 4.9 (iOS)
Target Android level
API 35
Store accounts
Client owned
Signing keys
On Ishan’s laptop
Developer fee renews
12 Dec
Personal data
Names, phone, live location
  1. 1 OctUpgrade to API 36 quoted, 18 hours
  2. 12 SepRelease 5.0 approved on Android
  3. 14 AugMaintenance retainer renewed, 20 hours
  4. NoteData protection clause missing from the 2024 contract.

Illustrative screens with sample data. Layouts, fields, names and terms are set up around how your app development company works.

An ordinary day

The same Tuesday, before and after.

The code is written the same way. What changes is that the studio around it stops running on memory.

WhenTodayWith Verity
9:30 TodayYou open the store consoles one by one to see which builds are still in review. With VerityThe Releases screen shows four in review and one rejected, with the client already told.
11:00 TodayA client asks for another feature on a call and you say yes to keep them happy. With VerityYou say yes and log it. It appears as an unpriced change with an estimate task for the lead.
1:00 TodayA WhatsApp screenshot of a crash reaches a developer after lunch. With VerityIt is a defect on the release with a severity and an owner. The client is told it is being fixed.
3:30 TodayA client asks why the launch slipped. You cannot show that sign-off took ten days. With VerityThe record shows the approval waited 10 days on their side, with the reminder dates.
6:00 TodayYou do not know which developer is free next week. With VerityThe schedule shows Meera free from the 22nd and Ishan double booked.
Month end TodayInvoices are raised from memory and retainer overruns are noticed in the next meeting. With VerityMilestones and retainer hours produce the invoice list, and overruns were flagged at 80 percent.

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 studio takes a project from proposal to maintenance, build Verity around that, bring your records in and stay on to keep them current.

  1. Week 1

    Discovery and mapping

    What we do
    Sit with you, your delivery lead and whoever invoices. Follow two live projects and one maintenance client from first message to last invoice, noting every chat, sheet and board involved.
    What we need from you
    Two to three hours of your time, plus access to your task boards, the time sheet and recent invoices.
    What you have at the end
    A written map of how work and money move through your studio, and a ranked list of leaks to close first.

  2. Weeks 2 to 3

    Configuration

    What we do
    Set up clients, apps, platforms, release states, change request rules, retainer hours, milestone invoices and the approval limits. We agree how time and task data reaches Verity from your existing tools.
    What we need from you
    Review the states and rules with your delivery lead. Correct where we misread your process.
    What you have at the end
    A working Verity with your clients and apps, ready for your history.

  3. Weeks 3 to 4

    Migration and training

    What we do
    Bring in clients, apps, open projects, open change requests, retainers and unpaid invoices. Train developers, account managers and finance on one real project each.
    What we need from you
    Your sheets and exports in any shape. One hour with each role.
    What you have at the end
    Every app, client and open invoice inside Verity, and a team that has logged real work in it.

  4. After go-live

    Operations partnership

    What we do
    Review the first month of releases, change requests and retainers with you, tune the rules, and add new apps, clients and platform changes as they arrive.
    What we need from you
    A short monthly review.
    What you have at the end
    A company system that keeps up with how the studio changes, with someone responsible for it.

Bring these on day one

  • A list of clients, apps and platforms
  • Your current project contracts and retainer terms
  • Recent time sheets and invoice lists
  • A list of store accounts, keys and renewal dates as far as known
  • Your usual estimate for common app types

Your time

About 8 to 10 hours of your own time across the four weeks, mostly in week 1. Your delivery lead and finance person need a few more.

After go-live

No one has to be hired to run Verity. Releases, defects and hours are recorded as part of the work your team already does.

Verity AI

Ask your studio a question. Get an answer, not a report to build.

Verity AI reads your own project, release, defect and invoice records. Ask in plain language, then turn the answer into tasks for the right people.

  • Your records only Answers come from your own app development companies 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 retainer clients are over their hours this month?

Six clients are over or close to their hours. FoodKart is at 137% and Booking Hub at 120%.

  • FoodKart137%
  • Booking Hub120%
  • Aarav Logistics92%
  • Wellbeing Co60%

Create tasks for the account managers to talk to the clients

Verity / Ask

Which apps need an upgrade for the new Android level?

Two apps still target API 35 and neither has an upgrade quote. Both are under a retainer.

  • Aarav LogisticsAPI 35
  • Booking HubAPI 35

Raise upgrade quotes for both clients

Verity / Ask

How far off are our estimates on food ordering apps?

Three finished food ordering apps took 66% more hours than quoted on average, mostly on payments and order tracking.

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. Your people still talk to clients. Verity makes sure the right person knows to.

When

A release is rejected in review

  • Fix task created with the review reason
  • Account manager told to update the client
  • New promised date recorded

When

A client asks for work outside the agreed scope

  • Logged as a change request
  • Estimate task to the lead
  • Approval requested before work starts

When

Retainer hours reach 80 percent

  • Alert to the account manager
  • Remaining hours and days shown
  • Option to quote extra hours

When

A milestone is marked complete

  • Invoice task to finance with the amount
  • Invoice added to the unpaid list when raised
  • Follow-up task if unpaid at 30 days

When

A platform announces a new required version

  • Affected apps listed
  • Upgrade quote task for apps outside a retainer
  • Dates added to the app record

When

A developer’s resignation is recorded

  • Handover checklist for each of their apps
  • Keys and accounts reviewed
  • Replacement assigned on the schedule

Rules and paperwork

The rules an app studio has to keep up with.

Verity does not give legal or tax advice and does not file anything for you. It keeps the records these rules depend on in order, so your lawyer or accountant is not rebuilding them from chats.

  • Platform rules of Apple and Google

    What is expected

    Both stores set the platform version, privacy and content rules your apps must meet. Google Play required new apps and updates to target Android 16 from 31 August 2026, with an extension to 1 November 2026 available on request.

    How Verity helps

    Platform version, privacy declarations and store review history are recorded on each app, with upcoming dates listed against the apps they affect.

    Android Developers

  • Personal data protection

    What is expected

    India’s data protection rules were notified on 13 November 2025. The main duties on notice, consent and safeguards are due to apply from 13 May 2027. Your clients are generally responsible for personal data, and you may handle it for them.

    How Verity helps

    Each app lists the personal data it collects, where it sits, who can access it and the contract that covers it.

    AZB Partners

  • Payment terms for micro and small suppliers

    What is expected

    If your studio is a registered micro or small enterprise, buyers who pay later than the time allowed by the MSMED Act generally lose the tax deduction until they pay. The limit is generally 45 days with a written agreement.

    How Verity helps

    Invoices show the acceptance date and age, so you can see which clients are past the limit and bring it up in a follow-up.

    TaxGuru

  • Ownership of code and accounts

    What is expected

    Your contract sets who owns the source code, the store accounts and the keys, and what happens at the end of the engagement.

    How Verity helps

    Each app records the owner of its accounts, where keys live and which contract clause applies.

Rules change and differ by situation. Confirm current requirements with your lawyer, accountant or the relevant authority.

Who sees what

Everyone sees the same records, through their own window.

A developer does not need to see invoice amounts. An account manager does not need to see salaries. Each role opens on what it needs.

  • Founder

    Which clients and projects make money?

    Estimates against actuals, retainer overruns, unpaid invoices, utilisation and risks to releases.

  • Delivery lead

    What is blocked, and who is free?

    Releases in review, defects by release, the schedule, change requests awaiting estimates.

  • Developer

    What should I work on and what changed?

    Their tasks, the defect details, approved changes and the app notes.

  • Account manager

    What does my client need to hear today?

    Client status, promised dates, approvals waiting, hours used and open invoices.

  • Finance

    What can we bill and what is outstanding?

    Milestones reached, retainer hours, invoices by age and renewals due.

Straight answers

What changes, and what stays the same.

Keep using

  • Your task boards, code hosting and build tools. We agree how time and status reach Verity.
  • The store consoles, where releases are still submitted by your team.
  • WhatsApp and email with clients. Your staff talk, and the decision is written on the project.
  • Your accounting software and your accountant.

Verity does not

  • Write, build or test your code.
  • Submit apps to the stores for you.
  • Send messages to clients on its own.
  • Run payroll or file your returns.

We bring your client list, apps, open projects and unpaid invoices across from the boards and sheets you use now, in stages, so deliveries continue while we do it.

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

Questions

Questions app studio owners ask.

Do I have to give up my project board?

No. Your developers can stay on the tools they like. Verity holds the company side: clients, apps, releases, change requests, hours and invoices. We agree how task and time data reaches it during setup.

Can Verity submit my app to the stores?

No. Your team submits builds. Verity records the release, the state and the review result, and creates the fix task when a build is rejected.

How does it know about a new platform rule?

Someone on your team enters the rule and the date once, and Verity lists the apps affected and creates the tasks. It does not read store emails on its own.

We are a team of eight. Is this too much?

A small studio loses the most to a single missed renewal or unpriced change. We set up only what you need, and the process is the same four weeks.

Can it track hours for fixed-price projects?

Yes. Hours are logged against the project so you can see actual against estimate, even when the client is billed a fixed price.

Can I see which clients are not worth keeping?

It shows hours, defects and payment delays per client against what they pay. The decision stays with you, but the numbers are in front of you.

Who can see client information and keys?

Only the people you allow. Access is set by role, and every view and change is recorded with who and when. We suggest keeping the keys themselves in a proper vault. Verity records where they are.

Does it work for a studio that builds websites too?

Yes. Apps, sites and retainers use the same records. You name the project types in your own words.

What does it cost?

It depends on the number of people, clients 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. Apple Newsroom, May 2025
  2. Android Developers, target API level requirements, updated 1 October 2026
  3. AZB Partners on the DPDP Rules, 2025
  4. TaxGuru

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

Start with the work you have already done and not billed.

Tell us how your studio runs and we will show you the unpriced changes, retainer overruns and unpaid milestones 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.