Custom software for firms: the integration layer, the portal and the numbers your partners actually read
Your practice system, your ledger, your document store and your email each hold half the truth, and the partners' report gets rebuilt in a spreadsheet every month. We build the software your vendors never will: one integration layer across QuickBooks Online, Xero, Karbon, Applied Epic, Bullhorn or whatever you run, a client portal off the record you already keep, and read-only dashboards.
What you get
3 things that decide this
- 01One integration layer instead of four half-connections. We use the API where your vendor exposes one, batch or SFTP where a carrier offers nothing else, and a reviewed queue your staff clear with a click where neither exists.
- 02A client or candidate portal built on the record you already keep, so status, documents and messages come from your practice system, AMS or ATS rather than from a second copy somebody has to maintain.
- 03Partner dashboards that are read-only by design. Realization, work in progress, book retention, fill rate and margin by desk, current, traceable to the source record, and built once instead of assembled every month.
From the systems that never talk to the numbers your partners read
These two stations sit at the end of your firm's chain, after the document and the recurring work. Pick the system you'd want written to; Xero, Canopy, AMS360, EZLynx, HawkSoft, JobAdder, ADP, Gusto and the rest follow the same pattern to the depth your account exposes.
Station 01 · Integration
- Today
- Your practice system, ledger, document store and email each hold half the truth. Your AMS and your rater have never spoken, and a carrier still sends you a batch file on a Tuesday.
- What we automate
- One layer that joins them. We use the API where your vendor exposes one, batch and SFTP where a carrier offers nothing else, and field mapping you can read. Where neither exists, your staff accept from a reviewed queue with one click.
- What stays human
- You decide what is allowed to write and what stays read-only. We check what each of your accounts opens up during the audit and design to that.
Writes to QuickBooks OnlineCustomers, invoices, bills and journal entries, to the depth your account exposes.
Station 02 · The partner's numbers and the client portal
- Today
- Realization, work in progress, book retention, fill rate and margin by desk get rebuilt in a spreadsheet each month. Your clients ring to ask what a portal could have told them.
- What we automate
- Read-only dashboards across your practice system, AMS, ATS and ledger. Per-client and per-carrier reports built on a schedule. A client or candidate portal with status, documents and two-way messaging.
- What stays human
- What to do about the client, the book or the desk that isn't paying is your call. We make the number visible, current and traceable to its source.
Writes to QuickBooks OnlineRead-only.
Station 03 · Intake and the document
- Today
- Your client emails March's statements as photos, to whoever they dealt with last year. A submission lands as an ACORD form and four supplements. A resume takes five to ten minutes of somebody's morning.
- What we automate
- One intake point per firm. An agent follows up on the missing item until it arrives. Extraction reads client PDFs, ACORD forms, loss runs and resumes, then writes into the system that owns that record.
- What stays human
- Your staff review what was extracted before it posts. Nothing reaches a return, a submission or a shortlist unread.
Writes to QuickBooks OnlineDocuments attached to the client; vendor bills and receipts queued for your bookkeeper to accept.
Intake, quotes, the close and the compliance gate come before these. The firms hub walks the whole chain.
Four builds, and what each one plugs into
The integration layer between systems that were never introduced
QuickBooks Online and Xero open a broad API your accountant controls. Karbon and Canopy open their own. Applied Epic, AMS360, EZLynx and HawkSoft each publish a different surface, some of it partner-gated, and Bullhorn covers candidates, jobs and placements. Where a carrier still sends a batch file we take the batch file, and where nothing is exposed your staff clear a reviewed queue instead of re-keying.
Custom software development →
Client and candidate portals off the record you already keep
A portal that holds its own copy of the truth becomes another thing to reconcile. We build yours on top of your practice system, AMS or ATS: status your client can see without ringing, document requests that feed the same intake pipeline, and two-way messaging logged against the client, matter or placement. Golancer, the freelancer operations platform we built, runs on that shape.
Golancer case study →
Partner dashboards, read-only by design
Realization, work in progress, book retention, fill rate and margin by desk usually live in a spreadsheet somebody rebuilds monthly, so the number your partners argue about is three weeks old. We build them as read-only views across your systems, current, with every figure clickable back to the record it came from. Nothing writes to your ledger or your trust account.
Workflow automation for firms →
Products we've built for firms, end to end
Some work isn't a layer on a vendor's product. It's the product. IRS Escape Plan is an AI tax-strategy platform where a model reads and plain code does the arithmetic. Golancer runs invoicing, scheduling and daily priorities for independent operators. Both are named in our case studies, and both are the shape of a build that starts as a spreadsheet nobody can hire around.
IRS Escape Plan case study →
Most of what a firm needs, somebody already sells. Here's how we tell you which parts, and which parts nobody does.
We'd rather talk you out of a build than into one, and the audit call is where that happens. If you want a practice-management app, a rater, an ATS or a reporting add-on that your peers already run happily, buy it. A packaged product carries its own roadmap, its own support and a price your vendor amortises across thousands of firms, and no custom build competes with that on the standard shapes.
Three things reliably don't come in a box. Anything that has to cross two vendors' products, because neither vendor is paid to reach into the other. Anything that follows your firm's own rules rather than the average firm's, which is most of what your partners argue about. And anything a client or a candidate touches, where the experience is your brand and a generic portal makes you look like everyone else.
So the honest answer usually splits. Buy the systems of record, build the layer between and above them. That's what we do, and on the audit call we'll name the packaged tool where one fits better than anything we'd write for you.
- 01Buy the system of record; build the layer that crosses two of them and the layer your clients see.
- 02We name the packaged tool on the call when one fits your problem better than a build.
- 03Read-only by default on your ledger and your trust or premium accounts; writes are opt-in, per field, agreed in the audit.
The professional signs, the model reads but never does the arithmetic, and the compliance gate blocks. We write that down first.
A firm's work is a regulated act: the CPA signs the return, the producer binds the policy, the adjuster determines the claim, the recruiter decides the placement, and the regulator expects to see how a model was used and governed. So every build starts with a one-page map of what the software reads, what it proposes, and where a professional signs.
What follows is simple to state, and we put it in writing. Documents are read and extracted by the model; numbers are computed by code and reviewed by a person. Compliance checks are gates that stop the next step, not dashboards that mention it later. Client data is scoped to the engagement, never firm-wide, with written no-training terms you can produce. And every automated touch is logged so a reviewer, an auditor or a regulator can read what happened, and when.
- 01Returns, binds, determinations and placements signed by the professional; the software prepares.
- 02Extraction by the model, arithmetic by code, review by a person; compliance gates that block.
- 03Read-only by default on your ledger and your trust or premium accounts, with every write opt-in, per field, and agreed in the audit.
“They will treat your vision like their own and build it that way.”
Ron Klabunde · Founder, SmartREI ↗
“I am extremely happy with the results and would highly recommend Hashlogics to anyone.”
Daniel Khin · CEO, PremiumAudit.io
Some of the systems we have shipped
- AuditFree. We list what each of your systems opens up, trace one number your partners argue about back to its source, and price the integration honestly.
- DiagnoseWe map the path into your practice, agency or ATS system and accounting, and sit with the people who do the intake and the close for an afternoon.
- BuildFixed price from the diagnostic. Tested on your real documents, quotes and placements, under NDA.
- RunMonitoring, a named engineer, and the first two months of maintenance free.
Best fit: a firm with ten or more staff, a system you've outgrown in places, and a recurring process you can feel at month end or renewal season. Not a fit yet: a solo practitioner who needs a practice-management app, and we'll say so. You can stop after any stage; the audit note is yours either way.
Before you book
01Should we build this, or buy something?+
Buy your systems of record, build the layer between and above them. A practice-management app, a rater, an ATS or a payroll product is a solved problem with a vendor roadmap behind it, and you should use one. What nobody sells is the sequence that crosses two of those products, the rule that's specific to your firm, or the portal your clients judge you by. On the audit call we'll name the packaged tool where one fits better.
02Can you integrate with QuickBooks Online, Applied Epic, Bullhorn, Karbon or whatever we run?+
To the depth your account exposes, and we confirm that during the audit rather than promising it on a call. QuickBooks Online and Xero open a broad API your accountant controls, Karbon and Canopy open their own, the agency systems each publish a different surface with some of it partner-gated, and Bullhorn covers candidates, jobs and placements. Where a carrier still moves data by batch file or SFTP, we take the batch file.
03What happens where there's no API at all?+
Your staff clear a reviewed queue instead of re-keying, and that's a deliberate design rather than a failure. The layer prepares the record, shows the source next to it, and a person accepts with one click into the system that has no write path. It's slower than a real integration and far faster than typing, and it means a missing API never blocks the rest of the build.
04Will anything write to our ledger or our trust account?+
Not unless you ask for it, field by field, in writing. Read-only is the default on your ledger and on any trust or premium account, because the risk of a wrong automated posting outweighs the time it saves. Where you do want a write, we agree the exact fields during the audit, gate it behind your reviewer's acceptance, and log every posting with who approved it.
05Who owns the code you write for us?+
You do, and it's in the contract rather than in a conversation. You get the repository, the deployment and the documentation, so another engineer can pick it up without ringing us. We stay on for the first two months of maintenance free, then under an SLA or a trained handover to your own people, whichever you'd rather have.
06How do you keep a client portal from becoming another system to maintain?+
By never letting it hold its own copy of the truth. The portal reads from your practice system, AMS or ATS and writes back to the same record, so a status change your team makes in the system they already use shows up for the client without anyone updating two places. Document requests feed the same intake pipeline as everything else.
07Is this the whole of what you do for firms?+
No. Document collection, extraction and routing sit on the document intake page, and quotes, the close, renewals and compliance gates sit on the workflow automation page. The firms hub walks the whole chain from the client document to the partner's numbers, and the audit tells you which piece pays first at your size.
A senior engineer, not a sales rep
Abdul Basit founded Hashlogics in 2017, and the team runs from Lahore with a US LLC. Clients rate the work 5.0 on Clutch, and in 2026 it was named Best AI-Native Software House of the Year at TechNova. PremiumAudit.io, the AI premium-audit automation platform, IRS Escape Plan, the AI tax-strategy platform, and Shift Link, the workforce-compliance platform, are three of the systems we built and can show you.
Your audit call is with an engineer who has read client document queues, quote logs and compliance spreadsheets like yours. Bring last month's numbers if you have them, and we'll work from those.
- NDA before the first conversation.
- No pitch on the call. A note you could hand to another firm.
- Fixed price after the diagnostic, so the number isn't a guess.
Go deeper
- AI, automation and custom software for firms →The whole chain, from the client document to the partner's numbers.
- Document intake automation for firms →Collection, extraction and routing before this layer starts.
- Workflow automation for firms →Quotes, the close, renewals and the gate that blocks.
- QuickBooks Online and Xero APIs: what a real integration involves →What each one exposes, and what it doesn't.
- Applied Epic, AMS360 and EZLynx APIs →Different surfaces, and which are partner-gated.
- Bullhorn API: what a real integration involves →Candidates, jobs, submissions and placements.
- Batch files still run the insurance industry →Why an SFTP drop is still a supported integration.
- Custom software development →How we scope, price and hand over a build.
