Professional services software development for consultancies and firms

Recorded, billable, billed and collected are four different states of the same hour. Hold them in one field with a flag and leakage lives in the gap the schema cannot express, so work in progress becomes an argument.

  • Four states of one hour
  • WIP as a balance, not a report
  • IFRS 15 progress measurement
  • Seven modules, hours shown
What this involves

Tell us what you are building

By submitting this form, I authorize Zyneto to collect and process my personal data in accordance with theZyneto Privacy Policy.

We reply to every enquiry within one business day.

What does professional services software development involve?

Professional services software development builds the systems a firm bills from: time capture, rate cards, work in progress, invoicing and revenue recognition. The packaged category is professional services automation, or PSA. The hard part is that recorded, billable, billed and collected are four states of the same hour, and one field with a flag cannot tell them apart.

Phase one hours
1,180 in the worked example
Timeline
14 to 22 weeks
Module span
1,040 to 1,860 hours
Modules scoped
7, each with its own range

The core idea

The four states of an hour

An hour recorded is not an hour billed, and an hour billed is not an hour collected. Hold one field and three become opinion.

Recorded

Someone claims an hour against a piece of work. It has an author and a timestamp, nothing more.

Billable

A rule makes the claim chargeable at a value, from the engagement and the card as at the work date.

Billed

The value reaches an invoice. Until it does it is work in progress: a balance the firm carries, not a report.

Collected

Cash arrives against the invoice. High utilisation with slow collection means busy and short of money at once.

The gaps are where leakage lives

Write offs between recorded and billable, unbilled work and disbursements between billable and billed, bad debt after.

Utilisation depends on which state you count

Finance counts billed hours, delivery counts recorded, both are right. Settle it in the model, not a meeting.

Scope

What professional services software development covers

Six pieces of work. Most engagements are three or four, and the first decides what the rest cost.

Build or buy

Configure a packaged PSA, build custom, or both

Three honest routes, and one case where none is us. The test: how many commercial levels your contracts need, whether your revenue schedule must be independent of billing, and whether you hold client money.

Configure a packaged PSA

Kantata, Certinia, Scoro, BigTime, Accelo, Productive and BQE Core all bundle time, billing and resourcing. Fastest when your model fits theirs.

Build custom

Worth it when the commercial model is what does not fit: caps at several levels, a schedule independent of billing, or a past date position.

Both, with a boundary on paper

Keep the ledger and the resourcing tool, build the layer between them, and settle which system owns the invoice first.

When we are not the fit

A whole platform replaced inside a quarter, legal, tax or audit advice, or a partner to hold client money. No case study in this sector yet, which argues for a small first phase.

Integration

The estate we expect to meet

Three families of system, and the constraint that decides the plan in each. The work is almost always integration, because these products are configurable rather than programmable.

System familyWhat it isThe constraint that decides the plan
Practice and professional services automationKantata, Certinia, Deltek, Unit4, Projectworks and Scoro cover mid market and larger firms, bundling time, billing and resourcing.How many commercial levels the product models. One that understands a project will not grow a second above it.
Sector specific practice managementClio, Actionstep and LEAP under legal practices. IRIS, Karbon and CCH under accounting firms. Deltek and Newforma under engineering and design.They carry the sector obligations natively, which is worth a lot, and are least flexible about the commercial model.
The ledger and everything around itXero, QuickBooks, NetSuite, Sage Intacct and Tally underneath, Stripe, GoCardless and Razorpay on collection, and an e-invoicing path where one is required.Rarely the API. Nearly always which system is authoritative for the invoice and which merely reports it.

A practice management system, a resourcing tool and a general ledger are three products; buying one does not give you the other two. Settle which owns the revenue schedule first, because retrofitting means restating closed periods. On what the engagement record tells you, see capacity and margin forecasting from engagement data.

Compliance

Which rules change what gets built?

Not a badge wall. These change the data model, the retention policy or the delivery date. Each row names where and when we read it, and each is a requirement on your firm.

InstrumentWhat it forces the software to doWhen it applied, and where we read it
IFRS 15, Revenue from Contracts with CustomersWhere a performance obligation is satisfied over time, progress must be measured and the method applied consistently: an input method such as labour hours, or an output method such as milestones. That makes the choice a system requirement. The US equivalent asks the same.Issued by the International Accounting Standards Board in May 2014, effective for annual periods beginning on or after 1 January 2018, per ifrs.org, read 17 November 2026.
SRA Accounts Rules, England and WalesA ledger specification with rule numbers. Client money stays separate from the firm's own, a client account cannot provide banking facilities, and a bill comes before costs are taken. Rules 8.2 and 8.3 require bank statements at least every five weeks plus a reconciliation signed off by the COFA or a manager.Version marked current in effect from 25 November 2019, per sra.org.uk, read 17 November 2026. One regulator's version of a general duty: whichever licenses your firm sets your detail.
European e-invoicing: Directive 2014/55/EU with Peppol BIS Billing 3.0The Directive creates a common European standard for the semantic data model of an electronic invoice's core elements, and Article 7 requires contracting authorities to receive and process compliant invoices. Peppol BIS Billing 3.0 binds the EN16931 model to UBL syntax, so a credit note's element names still say invoice.Dated 16 April 2014. Article 11(1) required Member States to apply the implementing provisions by 27 November 2018, per eur-lex.europa.eu. The current Peppol set is the May 2026 release, per docs.peppol.eu. Both read 13 November 2026.
GDPR, Regulation (EU) 2016/679Client files carry personal data about people who are not your client, which makes controller and processor roles a per engagement question. Retention is per data category, because record keeping duties outlast the engagement.Dated 27 April 2016. Article 99 states that it applies from 25 May 2018, per eur-lex.europa.eu, read 17 November 2026.

We build to these controls and hand you the evidence for your audit. A vendor assessment will also ask about ISO/IEC 27001, SOC 1 and SOC 2; Zyneto holds none. Three boundaries, stated plainly: we do not provide legal, tax or audit advice, we do not hold client money, and we are not an accredited service provider for e-invoicing or statutory filing, so confirm who yours is before a plan depends on a date. Rates, thresholds and windows differ by jurisdiction and move, so confirm yours with your regulator and accountant. On the reporting clock, see billing review and approval routing inside a workflow.

Transparency

The scope of a phase one, and the hours behind every module

We publish the hours and the module breakdown, and a fixed price follows discovery. Seven modules, each with its own range, and the arithmetic. The scope assumes a firm keeping its ledger and taking engagement, time, billing and recognition in house.

Phase one hours

1,180

Seven modules, each inside its range.

Typical timeline

14 to 22 weeks

As a squad. A year end compresses scope, not the calendar.

Useful hours

1,040 to 1,860

Every module at its minimum, through to its maximum.

What moves the hours, ranked
DriverHours
How many commercial levels you needOne project at one rate is a different model from caps at several levels.High impact
Whether rate cards are already datedDated reference data is integration work. Rates on timesheet rows means re-rating under live history.The largest swing
Whether revenue recognition is in scopeA schedule independent of billing is a second model, and the one discovered late most often.Adds real scope
Which ledger you keep, and what it exposes80 to 200 each
Whether client money is heldA position for a past date is bounded. Rebuilding one from a pooled history is not.150 to 260
How many entities, currencies and tax regimesPriced in one currency, delivered in another, reported in a third: a rate date per event.Medium
How much history migratesReplay testing scales with the variety of your rate structures, not with headcount.Rarely small
Hours by module
ModuleHours
Engagement, contract and rate card model160 to 280
Time and expense capture with validation120 to 220
Billing, work in progress and the invoice run180 to 320
Revenue recognition and the schedule160 to 280
Resourcing, capacity and forecasting140 to 260
Integrations: ledger, payments, identity, e-invoicing160 to 280
Client portal, reporting and audit trail120 to 220

Phase one, added up

  • Engagement and rate card 180 plus time and expense 150 plus billing and work in progress 210 plus revenue recognition 180 plus resourcing 160 plus integrations 180 plus portal and reporting 120 equals 1,180 hours. Each of the seven sits inside its own range above, so you can move any line and see the total move.
  • The full span is 1,040 hours at every minimum and 1,860 at every maximum.
  • Outside that number, with their own ranges: quality assurance at 20 to 25 percent of build, environments and deployment at 80 to 160 hours, and security review and penetration testing at 60 to 120.

Delivery

How we deliver professional services software development

Five phases, each named by the artifact it produces rather than by a generic stage.

  1. Phase 01

    Engagement decision record

    How contract, engagement and project relate, where terms may sit, and what a cap applies to.

  2. Phase 02

    Rate card and billing rules

    Every rate dimension, every write off reason, and what a retroactive change does to time already billed.

  3. Phase 03

    Revenue schedule design

    How progress is measured per contract type, how billing and revenue schedules differ, and what happens at close.

  4. Phase 04

    Time replay test pack

    A past year of time and billing replayed per engagement and compared entry by entry, not netted off.

  5. Phase 05

    Adoption and control pack

    Runbooks, the write off policy as implemented, and the control documentation your auditor asks for.

Frequently Asked Questions

What are professional services in software?

Two different things. Here it means software built for firms that sell expertise by the engagement: consultancies, agencies, law firms, accountants, engineers and architects. The packaged version is sold as professional services automation, or PSA. The other meaning is a software company's own consulting arm, and search results for the phrase mix the two.

What are examples of professional services?

Law, accountancy and audit, management and technology consulting, creative agencies, architecture and engineering, surveying, and recruitment. What they share is that the product is people's time, sold under an engagement with terms. That is why time, rate and engagement are the three objects their software is built on.

What is professional services automation, and do we need it?

Professional services automation, or PSA, is the packaged category that bundles time capture, billing and resourcing into one product. Most firms should start there. Build custom when the commercial model is what does not fit: caps at several levels in one contract, a revenue schedule independent of billing, or a client money position for a past date.

Should we configure a packaged PSA tool or build our own?

Answer three questions first. How many commercial levels do your contracts need, must your revenue schedule be independent of billing, and do you hold money belonging to a client? A packaged product usually handles the first and rarely the second, so the common outcome is a hybrid: keep the ledger and the resourcing tool, and build the layer between.

What does IFRS 15 require a billing system to be able to do?

Measure progress. Where a performance obligation is satisfied over time, IFRS 15 requires progress to be measured consistently, by an input method such as labour hours or an output method such as milestones. So the system needs a revenue schedule separate from billing, because a retainer billed evenly against work delivered unevenly recognises unevenly. The standard was issued by the International Accounting Standards Board in May 2014, per ifrs.org, read 17 November 2026.

How do the rules on client money change the ledger design?

They make a past date the question, so the system produces a per matter position for any past date rather than a reconciled bank balance. Under the SRA Accounts Rules in England and Wales, client money stays separate from the firm's own, and Rules 8.2 and 8.3 require bank statements at least every five weeks plus a reconciliation signed off by the COFA or a manager, per sra.org.uk, read 17 November 2026.

How long does phase one of a time and billing build take?

Fourteen to twenty two weeks as a squad. The worked example in the scope section is seven modules and 1,180 hours, and the same ranges sum to 1,040 hours at every minimum and 1,860 at every maximum, so a smaller or larger phase one is a question of which modules are in it.

What happens next

Four steps, each with a shape, so booking a call is a known quantity.

  1. A 30 minute technical call

    Bring how your system decides what an hour is worth, and how last month's work in progress figure was produced.

  2. The valuation question

    We establish whether your rate cards are dated, and whether work in progress is computed or assembled.

  3. A scoped phase one, module by module

    Against the hour ranges published here, with anything excluded named as excluded.

  4. You decide

    Whether we build it, your team does, or your incumbent extends. The document is yours either way.

Start with what an hour is worth

Bring one engagement and how last month's work in progress figure was produced. Thirty minutes usually tells both of us whether this is a fit.

Our Success Stories

Real feedback from the people we've proudly partnered with.

Brooklyn Foster profile

Brooklyn Foster

Sales Director |Cintas

United States

GoodFirms
"

Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.

"
Verified Review
Rating: 5 out of 5
Krystian Chlebek profile

Krystian Chlebek

Founder & CEO |Moneteo

TechBehemoths
"

We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.

"
Verified Review
Rating: 5 out of 5
Kevin Scott profile

Kevin Scott

CEO |E-Commerce Platform

Clutch
"

Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.

"
Verified Review
Rating: 5 out of 5

Explore further

Go deeper

Build the system

Adjacent capabilities

Other sectors

WhatsApp
Email
Book a Meeting