Verity for IT services companies

Twelve people on the bench, two clients waiting for staff, and a milestone nobody invoiced.

An IT services company sells people's time and delivered milestones, and earns when they match demand. Staff sit idle while a client waits, an SLA clock runs out in a mailbox, and a finished milestone waits a month for a sign-off. Verity connects the project, the people, the tickets and the invoice milestone, so you see the gap while it is still cheap to close.

Verity in one line

One system that knows every project, every engineer's allocation, every open ticket and every milestone, and tells you what is idle, late or unbilled before the month ends.

See your IT services company in Verity See the 15 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 ticketing tool, code repositories and accounts package stay where they are. Verity runs the company around them.

Verity / Company / This week

All projects

Live

On bench now

11

5 free next month

Over-allocated

4

above 100%

SLAs at risk

3

next 24 hours

Milestones unbilled

₹48 L

3 accepted

Hours used against estimate, fixed-price projects

  • Ledgerly migration1,310 of 1,000 h
  • RetailOne portal880 of 1,000 h
  • Medlink integration510 of 500 h
  • Axis support build305 of 500 h

Ledgerly migration is 310 hours over estimate with 2 unpriced change requests.

Review changes
  • Cloud engineer needed, RetailOne, start 3 Nov2 matches on bench from 27 OctUnfilled
  • Milestone 2, MedlinkAccepted 10 Oct, not invoicedInvoice

Illustrative screen with sample figures. Yours is set up with your own projects, bench, SLAs and milestones due.

How it runs today

The delivery is tracked and the business around it is not.

Engineers work in repositories and project boards. The project manager runs the sprint. That part is organised. What sits outside is the business view: who is free next month, which contract promises a four-hour response, which milestone is done but not signed off, and what each project actually earns after the team's cost.

The information lives in a resource sheet kept by one person, a ticket tool per client, contracts in a folder, timesheets in another tool and the invoice schedule in the finance team's sheet. The delivery head and the finance head hold the connection in their heads, and they disagree on dates.

So the company finds out late. A bench of ten that was visible two months ago. A premium SLA breached on a Sunday because no one watched the clock. A milestone completed in March and invoiced in May. And a small vendor paid late, which now has a tax effect. Nasscom's figures show industry revenue growing 6.1% in FY26 while headcount grew 2.3%, so the pressure to use each person well is real.

What most IT services companies run on

  • Resource allocation sheet
  • Ticketing tool per client
  • Timesheet tool
  • Contracts folder
  • Invoice schedule spreadsheet

Each tool is fine for its job. Nothing connects the contract, the people, the tickets and the invoice.

15 problems, one by one

Where an IT services company actually loses money.

These are the situations delivery heads, project managers and finance leads describe again and again. For each one: what it looks like, what it costs, and what Verity does about it.

  1. 01Resources

    The bench is invisible until it is expensive

    What it looks like

    A project ends on the 15th. The people from it have no next assignment. The resource sheet is updated on the 28th, when the delivery head finds eleven people unassigned.

    What it costs you

    Example arithmetic: eleven engineers at ₹1.2 lakh a month of cost sitting idle for a month is about ₹13 lakh. Reports on large Indian IT firms say bench has shrunk from over 20% to 8 to 15%, so an idle bench is one of the first things a client asks about.

    How Verity fixes it

    Every person has an allocation by project and date. Verity shows who rolls off in the next 30, 60 and 90 days, who is unassigned now and for how long, and what open demand could use them.

    See the screen
  2. 02Resources

    One engineer, three projects, at 100% each

    What it looks like

    A senior developer is allocated 100% to a client project and also named at 50% on two others. Each project manager believes they have her.

    What it costs you

    Over-allocation breaks deadlines on all three jobs and burns out the person everyone depends on.

    How Verity fixes it

    Allocation is entered as a percentage by project, and a person above 100% is flagged on the delivery head's screen with the clashing projects named.

    See the screen
  3. 03Resources

    Who can do this job?

    What it looks like

    A client needs a cloud migration engineer in two weeks. The delivery head recalls two names but not whether they are free, or who has done it before.

    What it costs you

    Hiring from outside for a skill you already have costs more and takes longer. Losing the deal because you could not staff it costs more still.

    How Verity fixes it

    Each person's skills, certifications and past projects are on their record. A request for a skill and a start date lists who matches, when they are free and who would have to be moved.

    See the screen
  4. 04Resources

    Notice period with no knowledge transfer

    What it looks like

    A lead engineer resigns with 60 days of notice. His handover is a few meetings and a document no one reads. A client asks a question about a module only he understood.

    What it costs you

    Delays, errors and sometimes a client who loses trust in the team.

    How Verity fixes it

    A resignation creates a handover plan: projects owned, systems and credentials held, documents to write and the person taking over each. The plan is tracked to completion before the last day.

    See the screen
  5. 05Service desk

    Tickets live in a shared inbox

    What it looks like

    A client's support mailbox gets 60 mails a day. Priorities are judged by whoever reads first. A "system down" mail sits behind a password reset for two hours.

    What it costs you

    Slow response on a serious ticket costs trust and, under many contracts, a service credit.

    How Verity fixes it

    Every request becomes a ticket with a client, priority, owner and a clock set by the contract's SLA. The queue is sorted by time left, not by arrival order.

    See the screen
  6. 06Service desk

    SLA breaches found at the monthly review

    What it looks like

    A contract promises a four-hour response and a one-day fix for critical incidents. Weekend tickets are watched by whoever remembers. The client's review lists three breaches.

    What it costs you

    Service credits, difficult renewals, and a reputation for being slow when it matters.

    How Verity fixes it

    Each ticket shows time to first response and time to resolution against the contract. Tickets nearing a breach are flagged to the owner and the service manager, and the monthly SLA view is built from the records.

    See the screen
  7. 07Service desk

    The same incident, again and again

    What it looks like

    A client's batch job fails every month-end. Each time a different engineer restarts it and closes the ticket. No one writes down the cause.

    What it costs you

    The same hours are spent every month on a problem that should have been fixed once.

    How Verity fixes it

    Tickets link to a problem record with the cause and the fix. A ticket that matches an open problem is tagged, and the count of repeat tickets by cause is shown to the service manager.

    See the screen
  8. 08Milestones

    A finished milestone that nobody invoiced

    What it looks like

    Phase 2 of a fixed-price project was delivered in March. The client's sign-off was verbal. The invoice for the milestone was raised in May.

    What it costs you

    Cash arrives two months later than it could have. At ₹25 lakh per milestone, that is real working capital the company has to find elsewhere.

    How Verity fixes it

    Each contract has milestones with a delivery date, acceptance state and invoice state. A milestone marked delivered with no acceptance after a set number of days is chased, and an accepted milestone with no invoice raises a task for finance.

    See the screen
  9. 09Milestones

    Acceptance never recorded

    What it looks like

    The client's manager says the module is fine on a call. Later, a new manager disputes that it was ever accepted and holds the payment.

    What it costs you

    A payment held on a technicality can be delayed for months.

    How Verity fixes it

    Acceptance is a recorded step with the approver's name, date and the document or message attached. The milestone cannot move to invoicing without it.

    See the screen
  10. 10Milestones

    Time-and-material hours that do not match the invoice

    What it looks like

    Timesheets are filled on Fridays from memory. The invoice is based on a spreadsheet summary that the client's team questions line by line.

    What it costs you

    Disputed hours are written off and the next invoice takes longer to approve.

    How Verity fixes it

    Hours are logged against the project and task as work happens, with a manager approval step. The invoice view sums approved hours by person and rate, so the finance team prepares the bill from agreed numbers.

    See the screen
  11. 11Vendors

    Small vendors and freelancers paid late

    What it looks like

    A specialist subcontractor is paid when the client pays you. Their bill is 70 days old. They are a registered micro enterprise.

    What it costs you

    Under Section 43B(h) of the Income-tax Act, amounts owed to micro and small suppliers beyond the allowed period are generally disallowed as a deduction until paid. The statutory limit is 45 days from acceptance. It can also lead to disputes with the vendor.

    How Verity fixes it

    Vendor bills are records with the date of acceptance, the vendor's registration status and the due date. Bills approaching the limit are listed for the finance head with the vendor and amount.

    See the screen
  12. 12Contracts

    Contracts, AMC and licences lapse quietly

    What it looks like

    A support contract ended on the 31st. The client's team kept raising tickets. For six weeks the company worked free while a renewal sat in a manager's inbox.

    What it costs you

    Unpaid support, and a weak position when renewing because the client has got used to free service.

    How Verity fixes it

    Every contract and AMC is a record with start, end, scope, SLA terms and a renewal owner. Renewal tasks appear 90, 60 and 30 days before expiry, and expired contracts are flagged on any new ticket.

    See the screen
  13. 13Projects

    Scope on a fixed-price project drifts

    What it looks like

    A client adds three small features by chat. The project manager says yes each time. The fixed fee has not moved and the team has worked 400 hours over the plan.

    What it costs you

    Example arithmetic: 400 extra hours at ₹1,000 a hour of cost is ₹4 lakh of margin gone on one project.

    How Verity fixes it

    Each project has a scope list and a change request step. Hours against the estimate are visible to the delivery head weekly, and a change either becomes a priced change request or is declined on the record.

    See the screen
  14. 14Compliance

    Overtime and weekend support with no record

    What it looks like

    A support engineer works extra hours on a go-live weekend. The overtime is agreed on a call and noted nowhere. A month later HR and the engineer disagree.

    What it costs you

    The Labour Codes took effect on 21 November 2025 and generally require consent for overtime, paid at twice the regular wage, though the central and state rules were still being finalised in 2026. Undocumented overtime is a dispute waiting to happen.

    How Verity fixes it

    Extra hours are logged against the person and the project with a manager approval and the reason. HR sees the month's overtime and the consent record before payroll is prepared in your own payroll process.

    See the screen
  15. 15Compliance

    Security incidents and client data

    What it looks like

    A server at a client site shows unusual logins at night. No one knows who should report it, to whom, or within what time. The access logs are kept for a week.

    What it costs you

    CERT-In's directions, effective 27 June 2022, generally expect covered entities to report listed incidents within six hours of noticing and to keep ICT logs for 180 days. The DPDP Rules add data duties from about 18 months after November 2025.

    How Verity fixes it

    Each client system has an owner, a named incident contact and a log retention date on the record. A reported incident creates a log with time noticed, who was told and when, so the six-hour clock is visible.

    See the screen

The numbers behind it

The numbers behind these problems.

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.

  • 6.1% vs 2.3%

    Nasscom's FY26 estimate for Indian tech revenue growth against headcount growth. Revenue is USD 315 billion; core IT services is USD 149 billion.

    ETV Bharat on Nasscom, 2026

  • 20% to 8 to 15%

    the reported shrinking of bench strength at large Indian IT firms, according to industry experts quoted by ET.

    Lets Data Science, 2026

  • 45 days

    the outer limit to pay a micro or small supplier for goods or services, after which the amount is generally not deductible until paid, under Section 43B(h) from AY 2024-25.

    TaxGuru

  • 6 hours

    the time within which listed cyber incidents must generally be reported to CERT-In after noticing them, with logs kept for 180 days, under directions effective 27 June 2022.

    PSA Legal, 2022

The bench figure is from a secondary aggregator quoting an ET report on large firms, and not on mid-size companies. Nasscom figures are as reported by PTI. Section 43B(h) and the Labour Codes are changing areas; confirm with your accountant.

What you will actually see

The screens you would use every day.

Six views, each built for one job. Names, columns and terms are set up in your company's own language.

Screen 1 of 5

The delivery head's morning view

Bench, over-allocated people, SLAs at risk, milestones to invoice and projects over estimate, on one screen. It replaces the Monday delivery review.

Fixes

  • 13 Scope on a fixed-price project drifts

Verity / Company / This week

All projects

On bench now

11

5 free next month

Over-allocated

4

above 100%

SLAs at risk

3

next 24 hours

Milestones unbilled

₹48 L

3 accepted

Hours used against estimate, fixed-price projects

  • Ledgerly migration1,310 of 1,000 h
  • RetailOne portal880 of 1,000 h
  • Medlink integration510 of 500 h
  • Axis support build305 of 500 h

Ledgerly migration is 310 hours over estimate with 2 unpriced change requests.

Review changes
  • Cloud engineer needed, RetailOne, start 3 Nov2 matches on bench from 27 OctUnfilled
  • Milestone 2, MedlinkAccepted 10 Oct, not invoicedInvoice

Screen 2 of 5

Who is free, who is stretched, who can do the job

Allocation by person and project, roll-offs, the bench and a skills search. A person above 100% is flagged, and open demand shows who could fill it.

Fixes

  • 01 The bench is invisible until it is expensive
  • 02 One engineer, three projects, at 100% each
  • 03 Who can do this job?
  • 04 Notice period with no knowledge transfer

Verity / Resources

Next 90 days

PersonSkillsAllocationRoll-offFree fromStatus
Nikhil RaoCloud, DevOps100% Ledgerly, 50% RetailOnen/an/a150%
Shreya IyerJava, APIs100% Medlink31 Oct3 NovRoll-off soon
Karan ShahQA automationUnassignedn/aNowBench 18 days
Divya PillaiReact, Node80% RetailOne15 Dec16 DecOK

Demand: cloud migration engineer

RetailOne. Start 3 Nov. 3 months

Skills needed
Cloud, DevOps
Matches
Karan (partial), Shreya (cross-train)
Gap
No exact match
  1. TodayRequest raised by project manager
  2. NextDelivery head decides move or hire

Screen 3 of 5

Service desk against the contract clock

Every ticket with its priority, owner and time left under the SLA. Repeat tickets are linked to a problem so the cause is fixed once.

Fixes

  • 05 Tickets live in a shared inbox
  • 06 SLA breaches found at the monthly review
  • 07 The same incident, again and again

Verity / Service desk

Open tickets, all clients

TicketClientPriorityOwnerSLA time leftStatus
Payment API downRetailOneCriticalAarav1 h 10 mAt risk
Month-end batch failedLedgerlyHighMeena3 h 20 mRepeat issue
Report export errorMedlinkMediumRohan1 dayOn track
Password resetAxisLowMeena2 daysOn track
  • Repeat: month-end batch8 tickets in 6 months
  • Repeat: report export4 tickets
  • Repeat: login lockout3 tickets

Month-end batch for Ledgerly has failed 8 times. A problem record is open with no owner.

Assign owner

Screen 4 of 5

Delivery, acceptance and the invoice

Each milestone with delivery, client acceptance and invoice state. Hours on time-and-material work are approved before the invoice is prepared. Verity does not run billing; your finance team does.

Fixes

  • 08 A finished milestone that nobody invoiced
  • 09 Acceptance never recorded
  • 10 Time-and-material hours that do not match the invoice

Verity / Milestones and hours

Fixed-price and time-and-material

MilestoneClientValueDeliveredAcceptedInvoice
M2 IntegrationMedlink₹18 L28 Sep10 OctNot raised
M3 ReportsMedlink₹12 L15 OctAwaitingNot due
Phase 2Ledgerly₹25 L14 MarVerbal onlyHeld
Sprint 14 hoursRetailOne₹7.6 L31 OctHours approvedReady

Phase 2 for Ledgerly was delivered in March with only verbal acceptance. Get written sign-off before billing.

Request sign-off

Screen 5 of 5

Contracts, vendors, and compliance records

Every contract, AMC and vendor bill with a date and an owner, plus overtime records and the security incident contacts for each client.

Fixes

  • 11 Small vendors and freelancers paid late
  • 12 Contracts, AMC and licences lapse quietly
  • 14 Overtime and weekend support with no record
  • 15 Security incidents and client data

Verity / Contracts and compliance

Due in the next 90 days

ItemPartyEnd or dueOwnerValueStatus
Support contractAxis31 OctMeena₹9 L/yrRenewal due
AMCMedlink15 DecRohan₹6 L/yr60 days
Vendor bill, QA freelancerPixel Test (micro)Accepted 12 AugFinance₹1.4 LDay 62 of 45
Vendor bill, designStudio Plum (small)Accepted 1 OctFinance₹0.8 LDay 15 of 45
  • Weekend go-live overtime approved, RetailOne teamConsent recorded for 5 people
  • Incident contact named, LedgerlyLog retention 180 days confirmed
  • Handover plan, resigning lead engineerLast day 20 Nov

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

An ordinary day

The same Monday, before and after.

What changes is not the engineering. It is that the day leaves a record, and the record does the chasing.

WhenTodayWith Verity
9:30 TodayThe delivery head asks each project manager who will be free next month. With VerityThe resources screen shows eleven on the bench, five rolling off, and the open demand they could fill.
11:00 TodayA client wants a cloud engineer in two weeks. The head remembers two names. With VerityA skills search shows who matches, when they are free and who would be moved.
1:00 TodayA critical ticket sits in the shared inbox behind two routine ones. With VerityThe queue is sorted by SLA time left and the critical ticket is already with its owner.
3:30 TodayA project manager agrees to a "small" change on a fixed-price job. With VerityThe change is logged as a request with an estimate, and the delivery head sees the hours against plan.
5:30 TodayFinance asks whether the milestone is accepted. No one is sure. With VerityThe milestone shows delivered on the 28th, accepted on the 10th with the client's note attached, and a task to invoice.
Month end TodayTimesheets, SLA reports and invoices are rebuilt from three tools. With VerityApproved hours, SLA results and milestone states are already on the records, so finance starts from clean numbers.

How we work with you

We set it up with you, in four weeks.

You do not get a login and a manual. We follow a project from contract to invoice, build Verity around how your people, tickets and milestones really move, bring in your data, then stay to make sure it keeps working.

  1. Week 1

    Discovery and mapping

    What we do
    Sit in on a delivery review and a service desk shift. Trace one contract from signature to milestone invoice, and one ticket from mail to closure.
    What we need from you
    Two to three hours of yours, your delivery head's and your finance lead's. Your resource sheet, a sample contract and a recent invoice schedule.
    What you have at the end
    A written map of your company: projects, people, skills, contracts, SLAs, milestones and the first gaps we will close.

  2. Weeks 2 to 3

    Configuration

    What we do
    Set up client and contract records, projects and milestones, allocation, skills, ticket priorities with SLA clocks, change requests, vendor bills and the six screens in your own terms.
    What we need from you
    Check the setup with a project manager and the service manager. Tell us where a priority, SLA or rule is wrong.
    What you have at the end
    A working Verity with your real clients, contracts and rules, ready for your data.

  3. Weeks 3 to 4

    Migration and training

    What we do
    Bring in people and skills, current allocations, open contracts, milestone schedules and open tickets from your sheets and tools. Train each role on its own screen using live projects.
    What we need from you
    Your resource sheet and contract list in whatever form they exist. One hour with each role.
    What you have at the end
    Your people, contracts and milestones inside Verity, and a team that has used it through a real week.

  4. After go-live

    Operations partnership

    What we do
    Stay on after launch. Review the first month of allocation, SLA and milestone data with you, tune the limits, and handle changes when you add a client, a service line or a team.
    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 company runs, with someone responsible for it.

Bring these on day one

  • Your resource or allocation sheet with skills
  • Three client contracts, including one with SLAs
  • Your milestone or invoice schedule
  • A month of ticket data in whatever form it exists
  • Your list of vendors and freelancers with registration status

Your time

About 10 to 14 hours of your own time across the four weeks, mostly in week 1. Your delivery head, service manager and finance lead need a few more each.

After go-live

Nobody is hired to run Verity. Allocations, tickets and milestones are recorded as part of work the team already does, and views come from those records.

Verity AI

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

Verity AI reads your own people, ticket, contract and milestone records. Ask in plain language, then turn the answer into tasks for the right people.

  • Your records only Answers come from your own IT services 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

Who will be on the bench in the next 30 days?

Sixteen people. Eleven are free now and five roll off by 15 November. Three match open demand.

  • Free now11
  • Rolling off by 15 Nov5
  • Match open demand3
  • No match13

Create allocation tasks for the delivery head

Verity / Ask

Which tickets will breach their SLA in the next four hours?

Three tickets across two clients. The payment API ticket for RetailOne has 1 hour 10 minutes left.

  • RetailOne1
  • Ledgerly2

Escalate to the service manager

Verity / Ask

Which accepted milestones have not been invoiced?

Three milestones worth ₹48 lakh. The oldest was accepted 38 days ago.

Create invoice tasks for finance

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 team still talks to clients and engineers; Verity makes sure the right person knows what to do.

When

A person is allocated above 100% across projects

  • Flag on the delivery head's screen
  • Clashing projects named
  • Decision recorded when rebalanced

When

A project is due to end within 30 days

  • Roll-off listed for the resourcing view
  • Open demand matched
  • Task to the delivery head for next assignment

When

A ticket reaches 75% of its SLA time

  • Flag to the owner and service manager
  • Escalation task if still unresolved
  • Breach recorded with the reason

When

A milestone is marked delivered and acceptance is not recorded after a set number of days

  • Task to the project manager to get written sign-off
  • Shown to the delivery head
  • Invoice step opens on acceptance

When

An accepted milestone has no invoice

  • Task to finance
  • Shown on the owner's screen
  • Invoice date recorded

When

A contract or AMC is 90 days from expiry

  • Renewal task to the owner
  • Scope and SLA terms shown
  • Outcome recorded: renewed, changed or ended

Rules and paperwork

The rules an IT services company 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 you are not hunting for them when someone asks.

  • MSME payment terms and Section 43B(h)

    What is expected

    From AY 2024-25, amounts owed to micro and small suppliers beyond the allowed period, which cannot exceed 45 days from acceptance of goods or services, are generally disallowed as a deduction until paid. Medium enterprises are excluded.

    How Verity helps

    Vendor bills carry the acceptance date, the vendor's registration status and a due date, with bills near the limit listed for finance.

    TaxGuru

  • CERT-In directions, 2022

    What is expected

    Issued on 28 April 2022 and effective 27 June 2022, they generally expect covered entities to report listed cyber incidents within six hours of noticing them and to keep ICT logs for 180 days within India.

    How Verity helps

    Each client system has an owner, an incident contact and a log retention date. A reported incident records the time noticed and who was told.

    PSA Legal

  • Labour Codes and overtime

    What is expected

    The four Labour Codes took effect on 21 November 2025. Overtime generally needs the worker's consent and is paid at twice the regular wage. Central and some state rules were still being finalised in 2026.

    How Verity helps

    Extra hours are logged with the reason, approver and consent. Verity does not run payroll.

    DLA Piper

  • Digital Personal Data Protection Rules, 2025

    What is expected

    Notified on 14 November 2025. Most duties apply 18 months after publication and cover data fiduciaries and processors. An IT services company that handles client personal data may be a processor.

    How Verity helps

    Client data access is by role with an audit trail, and retention dates are set per client.

    Scconline

  • GST and export of services

    What is expected

    Invoices to clients outside India may be zero-rated under conditions, and rules on receiving foreign payments are set by the RBI and have been changing. Your accountant and bank decide and file.

    How Verity helps

    Each invoice record carries the client, country, amount, invoice date and payment state.

Rules change and differ by situation. Confirm current requirements with your accountant or lawyer.

Who sees what

Everyone sees the same records, through their own window.

An engineer should not see everyone's billing rates. A client should not see another client. Each role opens on what it needs.

  • Managing director

    Is the company making money on its projects?

    Bench cost, project margin, unbilled milestones, renewals and client risk.

  • Delivery head

    Who is free, who is stretched, what is at risk?

    Allocation, roll-offs, skills search, hours against estimate and change requests.

  • Project manager

    Where is my project against the plan?

    Milestones, hours, tickets for the project, change requests and the team.

  • Service manager

    Which tickets are about to breach?

    Queue by SLA time, repeat problems, owners and monthly SLA results.

  • Finance lead

    What can I invoice and what do I owe?

    Accepted milestones, approved hours, vendor bills with due dates and overdue client invoices.

Straight answers

What changes, and what stays the same.

Keep using

  • Your ticketing tool where it is the front door for clients. We agree during setup how tickets and SLA clocks reach Verity.
  • Your code repositories and project boards, where engineers work.
  • Your accounts package, which still raises invoices and files returns.
  • Email and chat with clients. Your team replies
  • Verity tracks who owes a reply.

Verity does not

  • Host or monitor your clients' systems.
  • Send invoices, reminders or messages to clients on its own.
  • Run your payroll or file your returns.
  • Give legal advice on contracts or data protection.

We bring people and skills, allocations, contracts, milestone schedules, open tickets and vendor bills across from your sheets and tools, in stages, so projects keep running while it happens.

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

Questions

Questions IT company owners ask.

We already use a ticketing tool. Why Verity?

Your ticketing tool knows tickets. It does not know the contract, who is free to be assigned, or the milestone that is waiting. We agree during setup how tickets reach Verity so SLA clocks and repeat problems appear next to the rest of the business.

Does Verity replace our project boards?

No. Engineers keep their boards. Verity holds the business view: contracts, allocations, hours against estimate, milestones and invoices.

Can it handle fixed-price and time-and-material together?

Yes. Fixed-price work has milestones and hours against estimate; time-and-material work has approved hours by person and rate. Each is set up in your terms.

How does it show the bench?

From allocations. Each person is allocated to projects by percentage and date, so the unassigned or rolling-off list is a result, not a separate sheet.

Will it send SLA alerts to clients?

No. It alerts your team, who talk to the client. Verity records the response and the outcome.

Can it show profit by project?

Yes, once hours, rates and contract values are in. Verity shows revenue, hours, team cost and margin per project. Team cost uses the rates you set.

We are 40 people. Is that large enough?

A 40-person company has the same bench, SLA and milestone gaps with less slack to absorb them. We set up what you need in the same four weeks.

Who can see my data?

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

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 company runs.

Where the figures come from

Sources

  1. ETV Bharat on Nasscom, 2026
  2. Lets Data Science, 2026
  3. TaxGuru on Section 43B(h)
  4. PSA Legal on CERT-In directions
  5. DLA Piper on the Labour Codes
  6. Scconline

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 bench and the unbilled milestones.

Tell us how your company runs and we will show you the idle people, the tickets near breach and the accepted milestones with no invoice, 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.