Patent Docketing Software: Custom Build or Off the Shelf
Buy. Under roughly 2,500 active cases in two or three jurisdictions with conventional prosecution, PATTSY WAVE, FoundationIP or Alt Legal costs far less than a build and their rules are maintained by people who do nothing else.
On this page
Buy. Under roughly 2,500 active cases in two or three jurisdictions with conventional prosecution, PATTSY WAVE, FoundationIP or Alt Legal costs far less than a build and their rules are maintained by people who do nothing else. Cross the line when per case pricing starts influencing which families you keep, or when house prosecution rules cannot be expressed in a configuration screen.
What the off-the-shelf products actually do well
This is the one system in a law firm where a defect is a malpractice claim rather than an inconvenience, so start by taking the incumbents seriously. They are used by serious intellectual property operations and they have earned it.
Anaqua is the most complete option for a large corporate department, with genuine portfolio analytics. FoundationIP is a competent cloud docket with maintained rules. Alt Legal is excellent at automatic docketing from public registry data, particularly on the trademark side, and rebuilding that would be difficult to justify. PATTSY WAVE and Computer Packages both serve mid market firms with sound docketing discipline.
What you get on day one:
- Maintained rule sets across many patent offices, updated by people who read practice notices for a living and who carry the consequence of getting them wrong.
- The routine deadline shapes already modelled: a shortened statutory period with extensions available in monthly increments under 37 CFR 1.136(a), an issue fee due three months after a notice of allowance and not extendable, United States maintenance fees at three and a half, seven and a half and eleven and a half years with their grace period and surcharge.
- Reminder ladders, docket reports and the audit output an insurer expects to see.
- Conflict free operation during the weeks your own team is buried, which has real value.
If you run under about 400 active cases across two or three offices, a build is the wrong purchase and we will tell you so. Renew, and spend the money on a second docketing specialist, which reduces missed dates faster than any software change.
Where they stop: correcting a priority claim on a live family
The workflow every packaged product models badly is a family that changes shape after dates have been docketed.
A patent family is a graph. Applications, continuations, divisionals, priority claims, national phase entries under the Patent Cooperation Treaty, granted patents with their own renewal clocks. Most products model it as a parent link with children hanging off it. That is fine until somebody corrects a priority date.
Then it is not fine. A national phase entry runs from the earliest priority date rather than from the international filing date, and the thirty month period applies in most designated offices with a thirty-one month variant at the European Patent Office. A terminal disclaimer changes term. One correction can move dates in five countries at once, and if a divisional is pending it moves those too. In a system that stores dates on records, the correction is a two week audit of a family nobody trusts afterwards. In a system that derives dates from the graph, it is five minutes and a changelog showing exactly what moved and who is affected.
Two further places the seams show. Rules, because the vendor's interpretation reaches you when the vendor ships it, and because your own house rules are not in any office's rulebook at all. Docketing an internal response date at sixty percent of the official period, never relying on an extension for a client on a fixed fee, always docketing a continuation review two weeks before the issue fee. Those are your prosecution strategy expressed as deadlines, and a configuration request to a vendor is not ownership of them.
And inbound correspondence. A firm in Japan sends a reporting letter as a PDF attachment. A firm in Brazil quotes an annuity in local currency in the body of an email. A German associate attaches a communication under Rule 71(3) and asks for instructions on a window that assumes you read it today. All of it lands in a shared mailbox and gets keyed by hand, twice, once for the date and once for the cost estimate. Every product in this category leaves that with you.
The arithmetic: cost per case against a one time build
Docketing is priced per case in the portfolio, which is the detail that makes this arithmetic different from most software decisions. Your bill grows with the exact asset you are trying to protect.
Take your annual platform invoice, strip professional services, and divide by active cases. Most firms land somewhere between ten and thirty dollars per case per year. Use twenty for the worked example and put your own figure in.
At 400 cases that is $8,000 a year. At 2,500 cases, $50,000. At 6,000 cases, $120,000.
A first release at $110,000 with 18 percent annual upkeep is about $150,000 across three years, roughly $50,000 a year averaged, and that number does not move when the portfolio grows. So the licence crossover sits near 2,500 active cases at twenty dollars, or near 1,700 at thirty.
One adjustment matters more than the arithmetic. Ask your partners whether the per case fee has ever been mentioned in a decision about whether to keep a family alive. If the answer is yes, the pricing model is now shaping portfolio strategy, and that is a governance problem rather than a cost one. Firms cross this line earlier than the spreadsheet suggests, and they are usually right to.
What a custom build actually costs
These are Digital Heroes delivery bands rather than market averages. A first release covering the family graph, an effective dated rule engine for your highest volume jurisdictions, correspondence ingestion and enforced two person verification on non extendable dates runs $65,000 to $140,000 and ships in 12 to 18 weeks. Adding the annuity decision and reconciliation pipeline, foreign associate instruction handling with cost estimates, client approval flows and portfolio reporting brings it to $180,000 to $450,000 across 7 to 12 months.
Two costs that are larger here than anywhere else we work:
- Data migration is 10 to 25 percent of the build, and in this category it is closer to 25. You are not moving rows. You are reconstructing family relationships and re-deriving every live date, then running both systems in parallel until the numbers agree case by case. Nobody should cut over on trust. Granted and annuity only cases can stay on the incumbent for one cycle to keep the parallel period manageable.
- Year two is 15 to 20 percent of build cost annually. Offices change fee schedules and extension mechanics with effective dates, electronic filing requirements shift, and standards such as WIPO ST.96 evolve. This is a maintained system for as long as the portfolio lives.
What pushes the range up: the number of jurisdictions you actually prosecute in, since each rule set needs review by somebody who knows that office; trademark work alongside patents, which is effectively a second module; and integration with public data sources, because the United States Patent and Trademark Office and the European Patent Office expose data through very different models.
The four situations where building wins
- Regulatory fit. Rules must be effective dated data your docketing supervisor can edit, with a report of affected live cases before any change takes effect. When an office changes practice mid year, you need to see the blast radius before you accept it, and you need the audit log to show which rule version produced which date. That is a defence, not a feature.
- Scale economics. Above roughly 2,500 active cases across six or more jurisdictions, per case pricing grows with the portfolio while a build does not, and the gap widens every year you keep filing.
- A workflow that is your competitive advantage. House prosecution rules are the case. Internal deadlines ahead of official ones, continuation review gates, fixed fee clients where extensions are never assumed. Those rules are why clients hire you, and they should generate their own docket entries rather than living in a partner's memory.
- Integration sprawl across three or more systems. Corporate departments feel this hardest: docketing in one tool, matter budgets in a second, product line ownership in a third, invoices from thirty foreign associates in a mailbox. Joining those is what makes annuity decisions defensible, and no vendor will build the join because it makes them replaceable.
How to decide in a week
Run a re-derivation audit. Pick twenty-five live cases spread across your jurisdictions and weighted toward families with continuations or national phase entries. Have a second docketing specialist re-derive every open date from source documents alone, without looking at the current docket. Then compare.
Count three things: dates that disagree, dates that agree but for the wrong reason, and cases where nobody could reconstruct the derivation at all because the rule used is not recorded. If the first two counts are zero, your incumbent is doing its job and you should renew. If the third count is more than one or two, you have an audit trail problem, and that is the finding that changes an insurance conversation.
While that runs, pull last quarter's annuity instructions and count how many were instructed but never confirmed back against the case. The dangerous annuity is not the one you decided to drop. It is the one everybody believes was paid.
Then turn the findings into a specification. Digital Heroes runs a paid discovery phase that ends in a signed product requirements document covering the family graph, the rule data model with effective dates, the verification workflow and acceptance criteria. You own that document whether or not we build it, and you can take it to any other firm on your shortlist.
Who we are wrong for: practices under 400 active cases, trademark only practices well served by registry based automatic docketing, and firms wanting developers without a written specification. We fit portfolios where the rules and the family shape have outgrown a product. Over fifty specialists, more than 2,000 projects, and a named team you meet before signing. India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law. Verifiable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- PMI's Pulse of the Profession research found organizations waste an average of roughly 9.9% of every dollar invested in projects due to poor performance - equivalent to about $1 million wasted every 20 seconds collectively worldwide. Source: Project Management Institute (PMI) (2018) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- Large companies globally have captured, on average, only 31% of the expected revenue lift and 25% of the expected cost savings from their digital and AI transformations - a significant gap between expected and realized value. Source: McKinsey & Company (2023) →
Frequently asked questions
How much does custom patent docketing software cost?
A first release with the family graph, an effective dated rule engine for your main jurisdictions, correspondence ingestion and two person verification runs $65,000 to $140,000 over 12 to 18 weeks. Adding annuity decisions and reconciliation, foreign associate instructions with cost estimates, client approvals and portfolio reporting takes it to $180,000 to $450,000 across 7 to 12 months.
How long does migration take and can we run both systems in parallel?
Plan for a parallel period of at least one full annuity cycle rather than a cutover weekend. Migration here means re-deriving every live date from source documents and reconciling case by case against the incumbent, which is why it commonly reaches a quarter of the build cost. Leaving granted and annuity only cases on the old system for one cycle keeps the reconciliation manageable.
Who owns the docket data and the rule sets if an agency builds the system?
You should own the repository, the infrastructure accounts, the rule data and the right to hire anyone else to continue, settled in writing before kickoff. For a system protecting assets across twenty year terms, depending on one vendor's willingness to keep supporting you is a risk worth refusing. Digital Heroes contracts through India LLP, US LLC and UK LTD entities so assignment sits under your own law.
What happens if a docketed date turns out to be wrong after a date passes?
The question becomes what the firm knew and when, and a system where records are edited in place cannot answer it. Build the docket as an append only event log recording every entry, the rule version applied, each verification, every reminder sent and to whom, and every acknowledgement. That record is the difference between a defensible position and an argument about recollection.
Can we build only the annuity pipeline and keep our docketing product?
Yes, and for many corporate departments it is the right first slice. Build the decision states, due through instruction requested, decision received, instructed to agent, paid and confirmed or deliberately lapsed with a named approver, and pull case data from the incumbent. It targets the money and the risk without touching prosecution deadlines, which are the hardest part to migrate.
Should a corporate intellectual property department build rather than use a firm's system?
Often yes, once the portfolio passes a couple of thousand cases, because a department needs docketing joined to product lines, budgets and research systems rather than sitting inside outside counsel's tool. Smaller departments are usually better served buying and insisting on a full data export clause. The deciding question is whether annuity decisions require business context your firm cannot see.
What is the difference between docketing software and intellectual property management software?
Docketing computes and tracks deadlines against office rules. Intellectual property management adds portfolio strategy: budgets, product mapping, licensing, competitive analysis and reporting to a board. Anaqua sits toward the second, PATTSY WAVE toward the first. Buying a management platform expecting docketing rigour, or the reverse, is the most common scoping error in this category.
Can inbound reporting letters from foreign associates be processed automatically?
Extraction can identify the case by application number, classify the document type, pull the official date and capture the quoted cost with its currency, leaving a human to confirm rather than type. The design point is not speed. The extracted date should be checked against the rule engine's own computed date, with any disagreement escalated rather than accepted, giving two independent sources for a critical deadline.
How do we know a build will not introduce the very errors we are trying to avoid?
By insisting the system enforces controls a habit cannot. A non extendable deadline should not become active until a second person has confirmed it against the source document, and every computed date should record the rule version that produced it. Then run the new system in parallel until it and the incumbent agree on every live case for a full cycle.
What should we ask a developer before signing a docketing project?
Ask them to whiteboard a patent family. You want a graph with applications, relationships, priority claims and national phase entries, and they should ask unprompted what happens to dependent dates when a priority claim is corrected. Then ask how a rule that took effect on a specific date is stored. If the answer involves a code deployment rather than editable data, keep looking.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
What should the first version of a custom project management tool include, and what should wait?
Version one is the painful workflow plus the basics: tasks, projects, permissions, and one integration, shippable in 12 to 16 weeks. Everything that feels essential but is not should wait: Gantt views, custom report builders, native mobile apps, and public API access all belong in version two, once real usage shows what matters. Teams that run the MVP for a quarter before expanding consistently spend less and drop features that looked critical on paper.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
We're paying for 250 Monday seats. Would building our own tool be cheaper?
Cheaper only if you hold the tool for three years or more. 250 seats on Monday's Pro tier at about $19 per user per month is roughly $57,000 a year, while a custom platform costs $120,000 to $200,000 to build plus 15 to 20 percent annually to run, so cash break-even sits around year three. Building wins if you also gain workflow fit and unlimited seats; if Monday fits fine and you only dislike the invoice, negotiate an enterprise contract instead.
Which integrations should a custom project management tool have?
Start with the three that move money and attention: Slack or Teams for notifications, calendar sync for deadlines, and your accounting tool such as QuickBooks or Xero so tracked time flows into invoices without retyping. Development teams usually add GitHub or GitLab so tasks close when code merges. Each solid two-way integration adds roughly 1 to 2 weeks of build time, so rank them by hours saved per week rather than wishlist order.
Who can build a custom project management software system?
Digital Heroes builds custom project management software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other project management software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .