CosmoLex vs Smokeball 2027: Price, Fit and Trade-Offs
Two suites, one buying decision
Legal practice management software runs matters, time and billing, trust accounting, documents and calendars from one system. CosmoLex and Smokeball both sell that category, so the real question is which system fits your billing, document and intake work, and which one you can price before a sales call.
Start with ownership, because it changes who you buy from. CosmoLex now operates as part of ProfitSolv, a parent brand that CosmoLex's own about page describes as a collection of software solutions. ProfitSolv owns 4 practice management platforms according to LawNext (2025), naming CosmoLex, Orion, Rocket Matter and Tabs3. ProfitSolv announced a strategic investment on June 24, 2025, and the companies did not disclose its amount or terms. Secondary reports disagree about when the CosmoLex acquisition happened, so ask the vendor for its ownership history if that matters to your contract.
Cloud use is already common in this segment. Cloud practice management: 79–81% of UK solo and small firms according to Lawyers Weekly (2025). That is UK data from Clio's 2025 solo and small-firm report, so read it as direction rather than a US benchmark.
TL;DR: Price-check CosmoLex first, because it publishes per-user monthly rates. Test Smokeball on your own document templates and Outlook workflow, because its pages list more Office integration, but expect a quote before you see any number.
Our read is that the choice turns on three things you can check this week: whether you need a price on paper before a call, whether your daily work runs through Outlook and Word, and whether you need to automate intake outside either product. Each is covered below with the vendor facts that bear on it.
Key Takeaways
CosmoLex now sits inside ProfitSolv, so confirm the contracting entity and ownership history before you sign.
CosmoLex publishes per-user monthly prices on three plans. Smokeball publishes none and routes every tier to a quote.
CosmoLex lists an Open API on its Pro plan. Smokeball's API is documented publicly, starting with matter reads that need two authentication headers.
Smokeball's pages place more Microsoft 365 and document-automation features in its lower tiers, but they contradict each other on one platform detail.
Neither vendor's pages publish a seat cap, so ask for minimum seats and contract terms in writing.
Any intake automation is yours to design, approve and maintain, whichever product you choose.
How we evaluated these tools
We weighted six criteria by what a small firm actually decides on. The weights reflect our judgment about this buyer, not a survey result, and they are shown so you can change them. We checked each vendor's own pricing and documentation pages on October 25, 2026, and used independent sources for ownership and product scope. Review-site star ratings are left out because they change monthly and several review platforms would not load during our check.
| Criterion | Weight | Why it matters for a small firm |
|---|---|---|
| Published price clarity | 15% | Shows whether you can budget before a sales call |
| Billing and trust accounting scope | 20% | Trust handling is the compliance-heavy part of daily work |
| Document automation and Office integration | 20% | Most matter work runs through documents and email |
| Intake and workflow automation | 15% | This is where manual re-keying tends to build up |
| API and export access | 15% | Decides whether outside automation is possible at all |
| Setup, onboarding and written scope | 15% | Drives go-live time and surprise add-on costs |
Billing and document work together carry 40% of the weight because they touch most matters every day. Price clarity carries 15% because a quote-only vendor cannot be budgeted before a call, which costs time even when the software itself fits.
What each product includes
Table 2 separates what each vendor's pages list from what they leave unstated. "Not listed" means the pages we read did not mention the feature. It does not mean the feature is missing.
| Capability | CosmoLex (pages read) | Smokeball (pages read) |
|---|---|---|
| Trust and business accounting | Listed on Launch: trust accounting and ledgers | Listed on Bill: trust accounting and reporting |
| Invoicing and online payments | Listed on Launch | Listed on Bill |
| Document assembly and automation | Listed on Core: document editing and assembly | Listed on Grow: advanced document automation and templates |
| Microsoft Outlook and Word | Not listed | Listed on Boost and Grow |
| AI assistant | Listed on Core: document summaries, filters and intake form builder | Archie add-on on Boost, Grow and Prosper+ |
| Intake and lead management | Lead capture and intake on Core; intake workflow automation on Pro | Intake add-on on Boost; intake included on Prosper+ with lead management |
| Custom workflows | Intake workflow automation listed on Pro | Custom workflows and templates on Prosper+ |
| Public API | Open API listed on Pro | Public API reference; see the Smokeball profile below |
| Reporting | Audit-ready insights and dashboards on Core; advanced compliance reporting on Pro | Firm insights and profitability reporting on Prosper+ |
| Published prices | Yes, per user per month on three plans | No; quote-based on every tier |
CosmoLex's plans build on each other. Core adds to Launch, Pro adds to Core, and the pricing page says all plans include support, onboarding, and security and compliance features. Add-ons such as CRM, Websites, Google Ads and LexShare or LexSign sit outside the plan prices.
Smokeball's tiers also build on each other. Boost includes everything in Bill, Grow includes Boost, and Prosper+ includes Grow. The pages contradict each other on one detail, though. The FAQ says Grow includes a native desktop application, while the plan list describes Boost as fully browser-based and lists a Web App under Grow. Ask which applies before you assume a desktop install.
Our read: CosmoLex's document and intake features begin at Core, so a firm that wants document automation at the lowest published price should price Core rather than Launch. Smokeball's Outlook and Word integration sits lower in its range, on Boost, while its advanced document automation starts at Grow. For Outlook-heavy work, the Smokeball tiers look easier to justify on paper, but you still need a quote to see the cost.
Pricing and what eight seats cost
Pricing checked October 25, 2026. Launch to Pro: $49 to $129 per user per month according to CosmoLex (2026), with the Core plan listed at $99 in between. The same page shows a monthly and yearly toggle but does not display yearly prices.
Yearly billing saves $120 per user, and the Pro plan lists an Open API, according to CosmoLex (2026). The pricing page states no user limits, minimum seats or contract terms. It also says the free trial is limited to a single bank feed connection.
Smokeball publishes prices for 0 of its 4 tiers according to Smokeball (2026). Each tier, from Bill to Prosper+, routes to a "Get pricing" request. The page's FAQ says the quote depends on the number of users, the plan, the contract term and any optional products, and that a no-obligation quote is available.
Table 3 applies CosmoLex's published list prices to an illustrative eight-seat firm. The arithmetic is ours, not a vendor quote, and Smokeball rows stay quote-based because no figure is published.
| Vendor | Plan | Seats | Monthly at list | 12 months at list |
|---|---|---|---|---|
| CosmoLex | Launch | 8 | $392 | $4,704 |
| CosmoLex | Core | 8 | $792 | $9,504 |
| CosmoLex | Pro | 8 | $1,032 | $12,384 |
| Smokeball | Bill to Prosper+ | 8 | Quote-based | Quote-based |
Worked example (illustrative, not customer data): take an eight-seat firm that opens 40 matters a month and spends 12 minutes re-keying each intake. That is 480 minutes, or 8 hours, of re-keying a month. At the Core list price, eight seats cost 8 × $99 = $792 a month, or $9,504 over 12 months. If the yearly saving applies as CosmoLex's page states, eight seats save 8 × $120 = $960 a year, though the yearly price itself is not shown. A proposed intake check that halves the re-keying would return about 4 hours a month. In a Smokeball build, that check would read the Matter.openedDate field from the Matter object, so the draft intake summary carries the matter's open date.
Who this is for
Choose CosmoLex if you want per-user prices on paper before a call, all-in-one trust and billing from Launch, and a path to intake automation and an Open API on Pro.
Red flags: you need Outlook and Word integration confirmed in writing, since the pages we read do not list it; you need add-on prices for CRM, Websites, Google Ads or LexShare and LexSign, which the pricing page does not show; or you need a written seat cap before you can budget.
Choose Smokeball if Outlook, Word, document templates and e-signature drive most of your daily work and you are willing to request a quote to get numbers.
Red flags: you need a price before any sales contact; you need a written answer on whether Grow is browser-based or desktop; or your automation needs sit only in Prosper+ and you are not ready to buy that tier.
Matter intake, where the re-keying hurts
Most small firms feel the cost in intake. A new matter is typed into the practice system, copied into a conflict check, then typed again into a task list or a client letter. A proposed US Tech Automations design would sit on top of whichever product you pick and reduce that copying. It is a configurable workflow, not a live deployment, and it depends on the prerequisites below.
On Smokeball, the proposed trigger is a matter the firm has already opened. A scheduled check calls GET /matters/{matterId} with the firm's x-api-key and Authorization headers, then reads fields such as the matter's title, clients and open date. The output is a draft intake checklist placed in a review queue for a paralegal. Prerequisites are a Smokeball API key, a user token for an account that can access the matter (Smokeball returns 403 when an account lacks access), and written firm approval for each client field the design reads. The human review point is a named person who confirms the conflict check and the client's identity before anything goes into a file or to a client. We did not open a Smokeball webhook reference, so the design assumes a scheduled check rather than a push trigger.
On CosmoLex, the same output needs an Open API, which the pricing page lists on the Pro plan. We could not open a public CosmoLex developer reference, so the endpoint list, authentication method and rate limits must come from the vendor before the design is scoped. Until then the output stays the same: a draft checklist in a review queue, with the same named reviewer approving it. Either path should log every run, including failed reads, so a missed intake shows up in a queue instead of disappearing.
Build it yourself or buy the design
Zapier, Make and n8n can connect a form to either product if the product exposes a usable endpoint or connector. For a single flow with one owner, a do-it-yourself build is often the cheaper answer. These tools support run histories, retries and error branches when you configure them, and that is real capability.
The buyer still owns the rest. You design the observability, make retries safe so a duplicate matter is not created (idempotency), set escalation paths, control who holds the API keys, and maintain the flow when a vendor changes an endpoint. A proposed US Tech Automations design would configure those pieces up front, with the same run logs, retries and review queue described above. It does not remove the prerequisites, though. The firm still approves data access and assigns the reviewers.
Pick the do-it-yourself route if the flow is one step and you already have an owner for it. Pick a scoped design when several people depend on the flow and nobody owns it day to day.
Vendor profiles, with the evidence
CosmoLex
Best fit: a firm that wants published per-user prices, all-in-one trust and billing from Launch, and an upgrade path to intake automation and an Open API on Pro. The CodeX TechIndex describes CosmoLex as cloud legal practice management software that combines matter management, billing, time tracking, document management, payments, and trust and business accounting, last reviewed June 2026, according to CodeX TechIndex (2026).
Limits: the pricing page states no user limits, minimum seats or contract terms. Add-ons such as CRM, Websites, Google Ads and LexShare or LexSign are outside the plan prices, and the page notes that additional fees may apply for LexShare and LexSign. Trust accounting and ledgers sit on Launch, but the free trial is limited, so run your own reconciliation test before you commit.
Implementation: onboarding and support come with all plans, according to the pricing page. Confirm how the Open API is provisioned on Pro, and whether the intake workflow automation on Pro covers the handoff you need, before you map the design.
Smokeball
Best fit: a firm where Outlook, Word, document templates and e-signature sit at the center of the work. Boost lists Microsoft 365 Outlook, calendar and Word integration, a client portal, an automated letterhead template, eSignature and eFiling. Grow adds practice-area templates, calculators and advanced document automation. Prosper+ adds firm insights, profitability reporting, lead management and custom workflows.
Smokeball founded in 2010 according to CodeX TechIndex (2026), which lists Chicago as headquarters and a July 2026 review date. We found no public record of a 2026 ownership change, but we could not confirm current ownership from a primary source, so ask Smokeball for it in writing.
Limits: pricing is quote-based. The FAQ says there is no limit on firm users or clients at the same time, and no seat cap is published. Archie and Intake are add-ons on the lower tiers, so price them into any quote.
Implementation: the public API reference documents GET /matters/{matterId}, which returns a Matter object with HTTP 200, 403 when the account lacks access, and 404 when no matter exists, according to Smokeball API docs (2026). Each call sends both an x-api-key header and an Authorization header, and the reference lists US, Australian and UK API hosts. The Matter object includes fields such as openedDate, clientCode and tags, which is enough to build a read-only intake check before you consider any write access.
What to get in writing before you sign
Table 4 lists the requests that settle the open questions in this comparison. Ask for them in writing before you compare quotes.
| Request | What to get | Why it matters here |
|---|---|---|
| Yearly price | The per-user yearly figure, not only the saving | CosmoLex shows the saving but not the yearly price |
| Seat and term rules | Minimum seats, contract length and cancellation terms | Neither vendor's pages state them publicly |
| Open API scope | Endpoint list, authentication method and rate limits | CosmoLex lists an Open API on Pro, but we could not open a reference |
| Smokeball write access | Credentials, scopes and any write endpoints | The page we opened covers a read of a single matter |
| Platform detail | Whether Grow is browser-based or desktop | Smokeball's own pages disagree |
| Trust account test | A reconciliation run on your own bank feed | Trust accounting is the compliance-heavy part of the work |
| Ownership record | The contracting entity and ownership history | ProfitSolv ownership is public, but the acquisition timing is not settled |
Common mistakes buyers make
Comparing CosmoLex's per-user list price with a Smokeball quote as if they were the same unit.
Reading the yearly saving as the yearly price.
Assuming an add-on is inside the plan price. CRM, Websites, Google Ads and LexShare or LexSign are priced separately.
Buying the top tier for one feature a middle tier already includes. Smokeball lists intake as an add-on on Boost and includes it on Prosper+, so check where your feature sits.
Treating an API listing as an integration plan. Confirm scopes and write access before you design around them.
Glossary of terms in this comparison
Matter: a client case or file that holds time, documents, billing and tasks.
Trust accounting: handling client money in a trust account, kept separate from firm funds.
LEDES: a billing data format that many firms use to send invoices to corporate clients. CosmoLex lists LEDES support on Core.
Open API: a documented interface for reading or writing data from outside the product.
Intake: the step where a new client and matter are captured and checked.
eFiling: electronic filing with a court or agency. Smokeball lists it on Boost.
Bank feed: an automatic import of bank transactions, used in trust and business reconciliation.
Questions buyers ask before they sign
When not to use US Tech Automations: skip a US Tech Automations design if your only need is a feature the product already includes, such as Smokeball's custom workflows on Prosper+ or CosmoLex's intake workflow automation on Pro, because the vendor's own tool then carries no extra design work. Skip it too if you cannot provide API credentials or name a reviewer who checks each run. A single Zapier or Make step that copies one field can also be the better choice when you already own the account and the flow is simple.
Is CosmoLex still an independent company?
No. CosmoLex now operates as part of ProfitSolv, which LawNext reports also owns Orion, Rocket Matter and Tabs3.
Which product has the clearer price?
CosmoLex does. It publishes per-user monthly prices on Launch, Core and Pro, while Smokeball asks for a quote on every tier, so only CosmoLex can be compared on paper before a call.
Does Smokeball have a public API?
Yes. Its API reference documents matter reads through GET /matters/{matterId}, using an x-api-key header and an Authorization header. Confirm write access and scopes before you design around them.
Which one handles Outlook and Word better?
On the pages we read, Smokeball lists Microsoft 365 Outlook, calendar and Word integration on Boost, and CosmoLex's pages do not list it. Confirm the CosmoLex position in writing before you rule it out.
Are there user limits?
Neither vendor's pages publish a seat cap. CosmoLex's pricing page states no user limits or minimum seats, and Smokeball's FAQ says there is no limit on firm users or clients at the same time.
Should I buy an automation layer instead of a practice suite?
No. An automation layer runs on top of a suite, so choose the suite first on billing and document fit, then decide whether intake needs outside automation.
Decision in one paragraph
For most small firms the decision starts with two questions: do you need a published per-user price before you talk to anyone, and does your daily work run through Outlook and Word? If the first answer is yes, start with CosmoLex. If the second is yes and you can accept a quote, test Smokeball first. Either way, get the Table 4 answers in writing, run a trust reconciliation on your own data, and name the person who reviews any automated intake before anything goes live. If you want a scoped view of a reviewed intake check on either product, see how US Tech Automations configures this.
About the Author

Helping businesses leverage automation for operational efficiency.