Recorded, billable, billed and collected are four different states of the same hour, and most systems hold one field plus a boolean. Leakage lives in the gap the schema cannot express, and work in progress becomes a guess that finance defends once a month. We build the parts underneath that argument.
The commercial facts in one block, before any of the detail. Practice management software development and time and billing software development are the same system from two ends, with revenue recognition between them. The tiles cover: Typical integration set, Phase one timeline, Rate band, Phase one range, Stack we actually use and Our commitment.
Typical integration set
01An accounting ledger you are keeping, a payments provider, single sign on and directory for staff and clients, a document store with e-signature, an e-invoicing path where the jurisdiction requires one, and whichever delivery tools your practice already runs on.
Phase one timeline
0214 to 22 weeks for the worked example below, run as a squad rather than a single developer. A financial year end inside the window compresses scope rather than the calendar, because nobody changes a revenue schedule in the week before close.
Rate band
03$40 to $100 per hour by role and seniority. Portals and reporting near the floor, the engagement model and the revenue schedule near the ceiling. Mixed teams blend to around $65.
Phase one range
041,180 hours in the worked example, which is $47,200 to $118,000 across the rate band and about $76,700 at the blend. The cost section shows every module and its range, so you can argue with any line of it.
Stack we actually use
05Python with FastAPI, Node, PostgreSQL and Next.js, with Terraform for infrastructure and Grafana and Prometheus for metrics. Postgres carries the engagement, the rate card history and the revenue schedule, because all three are append problems before they are product ones.
Our commitment
06No quote before a discovery that produces the integration inventory and the engagement model decision. Three things we are not: 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.
Audience
Six positions we are usually called from, and the thing each one is missing. Not a fit: if you want a practice management platform replaced end to end inside a quarter, or a partner who will give legal, tax or audit advice or hold client money for you, we are the wrong firm and would rather say so on the first call.
Time comes in from a tool, rates live in a workbook, and the invoice run is a person. What is missing is one engagement record that the rate, the bill and the revenue schedule all read from.
Retainers roll over, overage is negotiated per client, and nobody can say which retainers are underwater until quarter end. What is missing is drawdown modelled as a ledger rather than as a monthly reset.
Money held for a client is not the firm's money, and proving that on a past date is the question that matters. What is missing is a per matter position rather than a reconciled bank balance.
A fixed fee still consumes time, and profitability is invisible unless recorded time is valued against the fee. What is missing is the arithmetic that turns hours into a margin per engagement rather than a utilisation figure.
Billing follows certified milestones while effort follows the programme, and the two rarely line up in the same month. What is missing is a revenue schedule that is separate from the billing schedule.
Work in progress is assembled by hand and defended in a meeting every month. What is missing is a valuation computed from the engagement, the rate card as at the date, and the write off policy applied consistently.
Professional services is one phrase for six businesses. What breaks is different in each, so what we build is different. The operations covered here are: Consultancies, Agencies and studios, Legal practices, Accounting and audit, Engineering and AEC and Managed services.
01 · Your operation
What breaks
The commercial structure and the delivery structure are different trees, and most systems only have one. A single contract can carry several engagements, an engagement can run several workstreams, and a cap or a fixed fee can sit above all of them. Rate cards are negotiated per client, per grade and per year, and a renegotiation with retroactive effect re-values time already recorded, which a system storing the rate on the timesheet row simply cannot do.
What we build
A three level model where contract, engagement and project are distinct objects with their own commercial terms, so a cap can sit at any of them. Rate cards as dated reference data keyed to client, grade and period, with the timesheet holding the grade rather than the rate. Re-rating as a supported operation with a record of what changed and why, instead of a bulk update nobody can reverse.
The stages an engagement moves through, and what we build at each one. The stages run: Take on and check conflicts, Agree scope and rate card, Record time and expense, Value the work in progress, Bill, adjust and collect and Recognise revenue over time.
An hour recorded on Tuesday has no value until it is attached to an engagement, priced against the rate card that applied on Tuesday, tested against a cap, and either billed or written off under a policy. Then, separately, it contributes to revenue recognised over the life of the contract, which is not the same event as the invoice. Here is the estate we expect to meet, and the decisions that determine whether work in progress is a computed number or a monthly argument.
Kantata, Certinia, Deltek, Unit4, Projectworks and Scoro cover mid market and larger firms, usually bundling time, billing and resourcing. The bundling is the thing to check, because a product that models one commercial level will not grow a second one, and firms discover that at the point where a cap needs to sit above several engagements.
Clio, Actionstep and LEAP sit under legal practices, IRIS, Karbon and CCH under accounting firms, and Deltek and Newforma under engineering and design. These carry the sector obligations natively, which is worth a great deal, and they tend to be the least flexible about the commercial model in exchange.
Xero, QuickBooks, NetSuite, Sage Intacct and Tally carry the accounting underneath most of this, with Stripe, GoCardless and Razorpay on collection and an e-invoicing path where the jurisdiction requires one. The integration question is rarely the API and nearly always which system is authoritative for the invoice and which merely reports it.
Recorded, billable, billed and collected are four states, and the transitions between them are where a firm's margin actually goes. A system holding hours plus a billable boolean can tell you utilisation and nothing about realisation, because the value of what was recorded and the value of what was billed are never both stored. Model the entry with its engagement, its grade, its status and every transition it has been through, including write offs with their reason and their author. Leakage then becomes a number you can attribute to a client, a partner or a type of work, rather than a gap that appears in the management accounts with no explanation attached.
An invoice is a demand for payment on a billing schedule that was negotiated. Recognised revenue is a measure of progress against a performance obligation, and under IFRS 15 and ASC 606 the two are deliberately separate: progress is measured by an input method such as costs incurred or labour hours, or by an output method such as milestones delivered. A monthly retainer billed evenly against work delivered unevenly recognises unevenly, and the difference is work in progress or deferred income depending on direction. Systems that treat the invoice as the revenue event force finance to rebuild that difference by hand every month, which is why so many firms cannot close quickly.
A rate belongs to a combination of client, grade and period, not to a person, and the same fee earner is billed at different rates on different engagements in the same week. Rate cards are renegotiated late and applied retroactively, which re-values time that has already been recorded and sometimes already billed. If the rate is copied onto the timesheet row at entry, that restatement is a bulk update with no memory of what it overwrote. Hold the card as dated reference data and store the grade on the entry, and a retroactive change becomes a re-rate with a record of what moved, which is also the only form of it that an auditor will accept.
Delivery and commerce are two trees and most systems ship one. A contract carries commercial terms and can span several engagements; an engagement carries the scope, the rate card and often the cap; a project is how delivery organises the work and can be created and closed without any commercial event at all. Collapsing these means a cap can only sit where the schema allows rather than where it was negotiated, and firms respond by creating fake projects to hold commercial terms, which then pollutes every delivery report. Model all three, allow terms at each level, and resist the temptation to let one of them stand in for the others.
The most useful hour of a first call is usually spent on how your system decides what a recorded hour is worth. Almost everything else on this page follows from that one answer, including the cost.
Five standards a buyer in this sector asks for by name, then every regional instrument in one place. Thresholds and tax rates move, so verify the regional row before contracting. The rules in scope are: ISO/IEC 27001, SOC 1 and SOC 2, GDPR and UK GDPR, IFRS 15 and ASC 606, PCI DSS and Everything regional, in one place.
The information security management certification procurement asks for by name, and in this sector it is frequently contractual rather than optional, because your clients are passing you their own confidential material. The scope statement matters more than the certificate: the question is whether client deliverables and working papers sit inside the certified boundary or immediately next to it.
SOC 2 covers security and availability and is the standard ask from clients running vendor assessments. SOC 1 covers controls feeding your clients' financial reporting, and it appears as soon as any part of your service touches their books, which for managed accounting or outsourced finance work is immediately.
Client files carry personal data about people who are not your clients, which makes controller and processor roles a per engagement question rather than a company wide answer. Retention collides with professional record keeping obligations that outlast the engagement by years, so it is set per data category, and privileged or otherwise protected material needs its own access model rather than a role on a shared folder.
Revenue from Contracts with Customers is the standard that governs when your work becomes revenue. IFRS 15 applies to annual reporting periods beginning on or after 1 January 2018. ASC 606 applies to public entities for annual reporting periods beginning after 15 December 2017 and to private companies and non-profits after 15 December 2018. Where a performance obligation is satisfied over time, progress is measured by an input method such as costs incurred or labour hours, or an output method such as milestones, and that choice is a system requirement rather than a note in the accounts.
It applies wherever card data touches fee collection, and the useful move is nearly always to keep it out of your estate entirely by tokenising at the gateway. Worth deciding deliberately, because a client portal that stores a card for convenience pulls your whole delivery platform into scope alongside it.
In India electronic invoicing under GST is mandatory for business to business supplies and exports where aggregate turnover exceeds ₹5 crore, in force since 1 August 2023, and since 1 April 2025 taxpayers with an annual aggregate turnover of ₹10 crore or more must upload an invoice to the Invoice Registration Portal within 30 days of issue, which turns late billing into a tax problem rather than only a cash flow one. Tax deducted at source under section 194J of the Income Tax Act runs at 10 percent on professional services, royalty and director remuneration and 2 percent on technical services, with the threshold raised to ₹50,000 per financial year, applied to each category of service independently, from 1 April 2025; because that deduction lands against the invoice rather than against the engagement, a system that cannot reconcile deducted amounts back to specific invoices will spend every year end doing it manually. For regulated practices generally, money held for a client is not the firm's money and the obligation is to prove the position per matter rather than per bank account, with the detail set by whichever regulator licenses you, so confirm the accounts rules that apply to your practice before designing the ledger. Firms operating across more than one jurisdiction should expect the electronic invoicing question to be answered differently in each and should treat the transmission path as a per entity decision rather than a platform wide one.
Ten failure modes with the counter-practice attached. Naming them is more useful than a list of reasons to pick us. The first three below are: The rate is copied onto the timesheet, Billable is a boolean and The invoice is treated as the revenue event.
A retroactive rate change then becomes a bulk update with no memory of what it overwrote, which no auditor will accept. Store the grade on the entry and hold the rate card as dated reference data, so a re-rate is an operation with a record rather than an overwrite.
Utilisation is then measurable and realisation is not, so leakage shows up in the management accounts with nothing to attribute it to. Model recorded, billable, billed and collected as states with transitions, and write offs with a reason and an author.
Under IFRS 15 and ASC 606 a contract satisfied over time recognises as progress is made, not when a document is sent. Keep the revenue schedule as its own object on the contract, or finance will rebuild the difference by hand every month.
When contract, engagement and project are one table, a cap can only sit where the schema allows rather than where it was negotiated, and people invent fake projects to hold terms. Model all three levels and allow terms at each.
Rollover, overage and unused balance are all invisible if the model starts each month from zero, and the client will remember what you have forgotten. Hold drawdown as a ledger and derive the position rather than resetting it.
A number defended in a meeting is a number that changes depending on who prepares it. Compute the valuation from the engagement, the rate card as at the date and a written write off policy, so the monthly conversation is about the policy rather than the arithmetic.
Checking at take on by asking a person puts the control at the point of least attention, and the failure is not recoverable once work has started. Hold restrictions as data and enforce them at assignment and at take on, with a re-check when parties change.
A reconciled bank balance says the bank agrees, not whose money it is, and the question is always about a past date. Keep a per matter position that cannot be netted against office balances and can be produced for any date.
In India an invoice from a taxpayer above the ₹10 crore threshold has to reach the Invoice Registration Portal within 30 days of issue, so delay stops being commercial and starts being fiscal. Put the reporting clock in the billing workflow where the person delaying can see it.
Matching the work in progress figure on cutover day proves the sum, not the entries or the rates behind it. Replay a full past year of time and billing per engagement and compare entry by entry, because a compensating pair of errors will always agree at the total.
The honest answer is usually the third one. Three judgements sit outside this table because they are not ours to make: 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.
| Component | Our recommendation | Our honest verdict |
|---|---|---|
| General ledger and statutory accounts | Buy | Tax logic, filing formats and audit expectations are already inside these products and they track the changes for you. Building one is a compliance backlog you would maintain forever. |
| Time and expense capture | Buy the core, build the edge | Buy the capture surface, because people will use whatever is fastest, then build the validation and the engagement rules behind it. The form is commodity; what a valid entry means on your engagements is not. |
| The engagement and rate card model | Build | This is where your commercial difference lives and it is the piece every other system needs to read. Owning it is what lets a cap sit where it was negotiated rather than where a vendor's schema allows. |
| Billing, work in progress and the invoice run | Buy the core, build the edge | Buy the invoice generation and the ledger posting, build the valuation and the write off policy. The document is commodity; how an hour becomes a defensible figure is the whole job. |
| Revenue recognition schedule | Build | Almost no practice management product produces a revenue schedule independent of billing, and that independence is exactly what the standard requires. This is the gap that most often needs building. |
| Resourcing and capacity planning | Buy | Scheduling people against demand is a solved problem with good products behind it. Integrate one and feed it your engagement data rather than rebuilding a calendar. |
| Conflicts, independence and information barriers | Build | The rules are yours, the party graph is yours, and enforcement has to sit inside assignment and take on. No product knows which clients you may not serve, and neither should it be guessing. |
| Client money ledger where you hold it | Buy | A regulated ledger with audit expectations attached. Use an established one and integrate to it, because the failure mode here is not a bug, it is a finding. |
| E-invoicing and statutory transmission | Buy | Only an accredited service provider may transmit, so this is not a build decision at all. Establish who yours is before the plan depends on the date. |
| Document assembly and e-signature | Buy the core, build the edge | Buy the signature and storage layer, then generate from the engagement record so an engagement letter and the system cannot drift apart. |
| Client portal and delivery reporting | Build | This is the surface your client judges the relationship through, and a bundled portal shows them the vendor's data model rather than your service. Building it is bounded work with a visible return. |
Transparency
Every competitor publishes a total with no hours behind it. Here is the rate, the hours and the multiplication, so you can argue with any line. The scope priced here is a firm keeping its accounting ledger and taking engagement, time, billing and revenue recognition in house.
Phase one range
$47,200 to $118,000
The 1,180 hour worked example at the ends of the rate band, about $76,700 at a $65 blend.
Typical timeline
14 to 22 weeks
As a squad. A year end inside the window compresses scope rather than the calendar.
Useful hours
1,040 to 1,860
Every module at its minimum, through to every module at its maximum.
| Driver | Hours |
|---|---|
| How many commercial levels you needA single project with a rate is a different model from contracts carrying several engagements with caps at more than one level, and the difference is structural rather than cosmetic. | High impact |
| Whether rate cards are already datedIf rates are held as dated reference data this is integration work. If they are copied onto timesheet rows, retroactive re-rating has to be introduced underneath a live billing history. | The largest swing |
| Whether revenue recognition is in scopeA revenue schedule independent of billing is a second model rather than a report on the first, and it is the module most often discovered late. | Adds real scope |
| Which ledger you keep, and what it exposesVendor API surface at your specific version, not at the version in the current documentation. This is the most common source of a mid-build surprise. | 80 to 200 each |
| Whether client money is heldA per matter position that can be produced for a past date is bounded work. Reconstructing one from a pooled history is not bounded, and is sometimes not possible at all. | 150 to 260 |
| How many entities, currencies and tax regimesOne is a section of work. Three is a programme with its own consolidation model, and it stays affordable only if the tax logic was kept out of the transaction path. | Medium |
| How much history migratesReplay testing scales with the variety of your engagement and rate structures rather than with headcount, so a small firm with unusual terms can cost more than a large uniform one. | Rarely small |
| Module | Hours |
|---|---|
| Engagement, contract and rate card model | 160 to 280 |
| Time and expense capture with validation | 120 to 220 |
| Billing, work in progress and the invoice run | 180 to 320 |
| Revenue recognition and the schedule | 160 to 280 |
| Resourcing, capacity and forecasting | 140 to 260 |
| Integrations: ledger, payments, identity, e-invoicing | 160 to 280 |
| Client portal, reporting and audit trail | 120 to 220 |
Engagement
Four models for professional services software development, each with the downside stated in the same breath. The models are: Fixed scope phase one, Dedicated squad, monthly, Practice migration and cutover and Year end readiness window. Pick by how settled the scope actually is, not by preference.
Upside
A defined scope, a fixed number and a date. It works best after discovery has produced the integration inventory and the engagement model decision, because that is the point at which scope is genuinely knowable.
Downside
Change costs more than it would hourly, and an accounting policy decision taken mid build can move scope without either of us choosing it.
Upside
A standing team that keeps the domain knowledge in the room, billed on time and materials so you pay for work actually done. Long integration and migration work suits this shape.
Downside
You carry the utilisation risk, and a quiet month still costs a month. We will tell you when there is not enough work to justify it.
Upside
Scoped to moving between practice platforms, priced on the variety of your engagement and rate structures rather than on headcount, with time and billing replay built into the plan rather than bolted on at the end.
Downside
Discovery is unusually long here, and it can conclude that some of your historic rates cannot be reconstructed at all.
Upside
Capacity held around your reporting calendar, so revenue recognition and consolidation work lands before close rather than during it.
Downside
You are paying for availability against a date that only matters once a year, and outside that window the arrangement is poor value.
Delivery
Five phases, each named by the artifact it produces rather than by a stage in a generic waterfall. The phases are: Engagement decision record, Rate card and billing rules, Revenue schedule design, Time replay test pack and Adoption and control pack.
Phase 01
How contract, engagement and project relate, where commercial terms may sit, and what a cap applies to. Written down before anything is built on top of it, because every later argument resolves against this document.
Phase 02
Every rate dimension, every write off reason, and exactly what a retroactive change does to time already recorded and already billed. This is the document a disputed invoice is defended from.
Phase 03
How progress is measured per contract type, how the billing schedule and the revenue schedule differ, and what happens at period close. Agreed with whoever signs your accounts rather than shown to them afterwards.
Phase 04
A full past year of time and billing replayed per engagement against the new model and compared entry by entry, with the differences explained rather than netted off. The work in progress total is not the test.
Phase 05
The runbooks, the write off policy as implemented, and the control documentation your finance team and your auditor will ask for, produced as part of the build rather than assembled afterwards under time pressure.
Non-functional
Copy this and run it against us, or against anyone else quoting for professional services software development. The groups are: Time, rates and replay, Billing, revenue and proof and Restrictions, change and scope. Copy any line straight into your own requirements document.
Can the system value a past week of recorded time using the rate card that applied then, as a query rather than a reconstruction? Is every state change on a time entry retained with its reason and its author, so a write off can be attributed? Can a retroactive rate change be applied as a re-rate with a record of what moved, rather than as a bulk update?
Is the revenue schedule a separate object from the billing schedule on the same contract, and can both be produced for a closed period? Can work in progress be computed from the engagement, the rate card and a written policy without anyone assembling it? Where client money is held, can a per matter position be produced for any past date without netting against office balances?
Are conflicts and independence restrictions held as data and enforced at assignment and at take on, rather than checked by a person? Are tax thresholds, deduction rates and reporting windows held as dated configuration so a rule change is a data change rather than a release? And confirm the boundary: we do not provide legal, tax or audit advice, we do not hold client money, and we do not transmit statutory filings or e-invoices for you.
The worked example is 1,180 hours, which is $47,200 to $118,000 across our $40 to $100 rate band and about $76,700 at a $65 blend, landing in 14 to 22 weeks with a squad. The module ranges sum to 1,040 to 1,860 hours, so a smaller or larger phase one is a question of which modules are in it. We do not quote a fixed number before a discovery that produces the integration inventory.
You do, all three, from the first commit. Repositories, cloud accounts, domains and third party service accounts are in your name or transferred to it at handover. What transfers alongside them is the engagement decision record and the rate card and billing rules, which is the part that makes the code readable by whoever comes after us.
Because under IFRS 15 and ASC 606 a services contract satisfied over time is recognised as progress is made, and progress is measured by an input method such as costs incurred or labour hours, or an output method such as milestones. A retainer billed evenly against work delivered unevenly recognises unevenly, and the difference is work in progress or deferred income. If your system treats the invoice as the revenue event, finance rebuilds that difference by hand every month, which is usually the real reason a close takes two weeks.
That is usually the actual brief, whatever the request says on the first call. It means computing the valuation from the engagement, the rate card as it stood at the date, and a write off policy that is written down and applied consistently, rather than assembling it in a spreadsheet. The test is whether last quarter's figure can be reproduced today without anyone remembering how it was prepared.
Because we would rather say that than describe a software client as a practice and hope nobody checks. What is on this page instead is the modelling, the standard and the arithmetic, all of which you can verify without trusting us. The code, decision records and specifications are yours from the first commit, which is the part that holds whether or not we turn out to be a fit.
Yes, and that is the more common shape of this work. The first question is how many commercial levels your specific product models, because a platform that only understands a project cannot hold a cap that was negotiated across several engagements, and everything built beside it becomes a workaround. We would much rather establish that in discovery than in build.
As a re-rate rather than an update. Because the timesheet holds the grade and the rate card is dated reference data, applying a new card from a past date regenerates the value of the affected entries and records what moved and why. Anything already billed becomes an adjustment with a traceable cause rather than a credit note nobody can explain, which is also the only version an auditor will accept.
We build to the requirement and we do not hold the money. The requirement in practice is a per matter position that can be produced for any past date and that cannot be netted against office balances, which is a modelling problem before it is a banking one. The specific accounts rules depend on whichever regulator licenses your practice, so confirm those with them before the ledger is designed rather than after.
It turns a cash flow habit into a tax problem. Electronic invoicing is mandatory for business to business supplies and exports above ₹5 crore of aggregate turnover, in force since 1 August 2023, and since 1 April 2025 taxpayers at ₹10 crore or above must upload an invoice to the Invoice Registration Portal within 30 days of issue. The practical build consequence is putting that clock inside the billing workflow, where the person holding the invoice can see it, rather than in a finance report they never open.
By replaying it. A full past year of time and billing is regenerated per engagement under the new model and compared entry by entry against what the old system produced. Matching the work in progress total is not the test, because it says nothing about which entries or which rates produced it, and a compensating pair of errors always agrees at the total.
We build the enforcement; the rules are yours. In practice that means holding restrictions as data rather than as a policy document, checking them at take on against a party graph that includes parties who are not clients, enforcing them again at assignment, and re-checking when parties change on a live matter. What we will not do is decide which engagements you may accept, which is a professional judgement and not a software one.
Four steps with a shape attached to each, so booking a call is a known quantity.
Bring how your system decides what an hour is worth, and how last month's work in progress figure was produced. Those two answers size the project faster than an hour of description would.
We establish whether your rate cards are dated and whether work in progress is computed or assembled. The answer usually explains most of the symptoms you called about.
Module by module against the ranges published on this page, with anything excluded named as excluded. If your platform already does most of it, the document says so.
With the scope in hand you choose whether we build it, your team does, or your incumbent extends. The document is useful in all three cases and it is yours either way.
Bring one engagement and how last month's work in progress figure was produced. Thirty minutes on those two usually tells both of us whether this is a fit, and you leave with the hours either way.
Real feedback from the people we've proudly partnered with.
Sales Director |Cintas
United States
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.
Founder & CEO |Moneteo
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.
CEO |E-Commerce Platform
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.
Explore further
Engagement, rate card history and the ledger
Client portals and practice consoles
Valuation, recognition and reporting runs
Engagement letters and working papers
Billing review and approval routing
Pipeline, capacity and margin forecasting
Productising a practice into a platform
Trust accounts and reconciliation
Every sector we build for, in one place
Document, automation and cost work that applies directly to time, billing and delivery systems.
