For Alaska law, accounting, engineering & consulting firms
Professional firms lose revenue in unrecorded time and lose days to document review. We build agents that capture the work as it happens and read the documents with citations, so your people bill what they actually did.
Built in Anchorage · we publish our source code · no long-term lock-in
Written by Kristian Baer, Northtek · Anchorage, Alaska · Updated 2026-08-21
The short answer
Two places, and neither is the one vendors advertise. The first is time capture: most firms lose a meaningful share of billable hours simply because work was not recorded contemporaneously, and an agent that reconstructs the day from calendar, email, and document activity into draft entries recovers revenue you already earned. The second is document review, where an agent reads a large record and answers questions with a citation to the exact page, turning a two-day read into a two-hour verified pass. What does not work is asking a model to produce legal, accounting, or engineering conclusions. Every output is a draft, every claim carries a citation, and a licensed professional reviews it. In Alaska the additional pressure is that firms here are small relative to the matters they handle, so leverage matters more than headcount.
The operating reality
Alaska professional firms handle sophisticated work with limited staff, often for clients spread across a state where getting to a meeting can take a day.
A ten-minute call that never gets entered is gone. Across a firm and a year the number is large, and nobody sees it because it never appears anywhere.
Discovery sets, permit records, and financial documentation arrive faster than anyone can read them, and the answer is usually on a handful of pages.
Filing deadlines, statutory dates, and reporting obligations do not forgive an oversight, and calendar discipline is manual in most firms.
The quality of a new matter file depends on who took the call. Inconsistent intake creates problems that surface months later.
Six workflows we build
Every one produces a draft for a licensed professional. None produces a conclusion.
01
02
03
04
05
06
First 30 days
It is measurable in a single billing cycle and it touches no client-facing work product, which makes it the safest place to evaluate how we work.
We compare recorded hours to calendar and system activity for a sample period. The gap is your recovered revenue estimate, and it comes from your own data rather than an industry benchmark.
Draft entries have to read the way your firm writes them and satisfy your clients’ billing guidelines, so we build against your actual approved entries.
Two people run it for one billing cycle. If recorded hours do not measurably rise, we say so rather than expanding the pilot.
What you own at day 30
A time capture agent connected to your practice management system, a measured recovery figure from one billing cycle, the source code and configuration, and confidentiality architecture your managing partner has reviewed in writing.
What we built, in the open
Document review is only valuable if the citations are real. A system that produces a fluent summary with an invented reference has not saved your associate time, it has added a verification task with a hidden failure mode. Building one that declines instead is harder, and it is what we spent our research on.
A verification gate that requires every statement to trace to a page in the record and reports silence rather than inferring. We publish its false-accept rate, which is the number your risk committee should ask any vendor for.
Long-context research with the benchmark harness published, which is the reason a large discovery set can be reasoned over without quietly dropping the middle of it.
Our own memory server, which is why privileged and client-confidential material can run inside infrastructure your firm controls rather than transiting a third-party service.
Public, with the harness. Any firm can claim accuracy; a published error rate is the version you can put in front of your managing partner.
Scope, stated up front
Professional judgment does not delegate, and a tool that blurs that is a malpractice question. Three hard limits.
It does not give professional advice
No legal conclusions, no audit opinions, no engineering judgments. It reads, summarizes, cites, and drafts. A licensed professional owns every output.
Every claim carries a source
Where the record does not support a statement, it says so instead of filling the gap. Confident invention is the failure mode that matters most in this industry.
Confidentiality constrains the architecture
Client-confidential material runs inside infrastructure you control. If that is not possible for a workflow, we do not build that workflow.
Where your data goes
Confidentiality obligations set the architecture, and your managing partner should read it before development starts. Four commitments we put in the agreement.
Only if it is architected carelessly, which is why the architecture comes first. Client material runs inside infrastructure you control, is never used to train a model, and access is logged. We put the architecture in writing for your managing partner or ethics counsel to review before any development begins.
No. It reads documents, answers with citations, and drafts. Conclusions, opinions, and advice come from licensed professionals in your firm. We build the boundary in and we write it into the scope document.
We will not quote you an industry number, because a number from someone else’s practice tells you nothing about yours. We measure your specific gap in the first two weeks against your own calendar and system activity, then size the engagement to what that recovery is worth. You get a real figure from your own firm before you commit to a build.
Those stay as the system of record. We build the layer that fills them in properly. Practice management migrations are painful and rarely solve the underlying data quality problem.
That is one of the strongest fits, because the value is in finding and citing rather than concluding. It reads the set, answers questions with page-level citations, and reports where the record is silent. Your attorney verifies the citations, which takes minutes instead of days.
The same four workflows apply: intake, cited document review, time capture, and proposal drafting. Engineering firms additionally get value from permit and specification search, which overlaps with our resource development playbook.
Two weeks of calendar and system activity against recorded hours tells you whether this is worth doing. Sixty minutes to set it up, no cost.
Anchorage, Alaska · info@northtek.io · (907) 903-4353