Your intake, drafts, meeting notes and follow-through, connected around the standards you already use. One build, owned by you, with people approving client-facing work. Software and usage charges remain separate.
Inputs, approved sources, human gates and exception paths, scoped in your blueprint. This is the design to inspect; provider settings and acceptance evidence must be verified for your actual build.
A focused 30-minute conversation. Same-day written findings once the call and any agreed outstanding inputs are complete. No obligation to build.
| WORK PREPARED | The workflows in your agreed scope |
| YOUR AUTHORITY | Approve client-facing work |
| YOU OWN | Scoped workflows, prompts and runbook |
| BUILD PRICE | Audit recommends; you choose; fixed before signing |
| CARE | Optional, with defined hours and terms |
| OTHER COSTS | Software, cloud and usage stay separate |
| INPUTS | Approved records, templates and sources |
| CONTEXT | Client-owned; isolated access |
| PERMISSIONS | Defined roles, minimum access, logs |
| DATA FLOWS | Approved and documented |
| RELEASE GATE | Approve current content and recipient |
| MODEL | A swappable component; inference location is the firm's custody decision |
| EVIDENCE | Provider configuration and tests before activation |
Built for law firms first. The three samples below follow one fictional employment firm from audit to care.
Sample · Illustrative. Whitfield & Marsh is a fictional nine-attorney employment firm built to show the deliverables start to finish. No client data, no client results.
Firm Systems AuditSample · Illustrative
Where your hours actually go, mapped system by system against your own numbers, with the capacity math shown line by line.deliverable 1 of 3 · precedes any commitment · fictional sample: Whitfield & Marsh LLP
Open the sample →
Build BlueprintSample · Illustrative
Scope, systems, acceptance criteria, and the fixed price, in writing, before the build starts. No number, no invoice.deliverable 2 of 3 · the contract-grade document · fictional sample
Open the sample →
Monthly Care ReportSample · Illustrative
What the machine did, what was corrected, what got sharper. Accountability for the system, monthly, in writing.deliverable 3 of 3 · under the optional care plan · fictional sample
Open the sample →
subscription scenario = seats × monthly rate × months. benefits and remaining manual work belong in the comparison too.
Draft a demand letter for unpaid overtime. Cite controlling authority.
"Pursuant to Smith v. Atlantic Logistics, 412 F.4th 88 (2d Cir. 2019), your client faces immediate liability."
citation fabricated: no such case exists in any reporter"We will pursue treble damages under the FLSA unless payment is received."
wrong remedy: the FLSA provides liquidated damages, not treble"We trust this letter resolves the matter amicably."
no firm template, no matter facts, no venue awareness"Pursuant to 29 U.S.C. § 216(b), your client is liable for the unpaid balance and an equal amount as liquidated damages."
illustrated check: retrieve statute and compare wording with source textDemand follows the firm's remedy framework for wage claims in this venue.
illustrated grounding: retrieve the firm-approved remedy frameworkRendered in the firm's letterhead template with a provenance appendix.
illustrated review: attach sources and flag unverifiable claims inlineSame prompt. Grounding and source checks make the draft easier to inspect, not immune to error.
Checked is universal. Verified is one outcome. The state travels with the draft, so a reviewer reads the check beside the sentence it concerns, not in a separate report.
| State | What the check found | What happens to the draft |
|---|---|---|
| ●Verified | The authority exists in the primary record and the quotation matches its source text. | Cited as drafted. Source and check recorded in the provenance appendix. |
| ▲Verified, characterization flagged | The authority exists and the quotation matches, but the draft's account of what it holds needs an attorney's reading. | Cited, with the flag beside the sentence. The attorney confirms or rewrites the characterization. |
| ○Unverifiable | The authority or the quotation could not be matched against a primary record. | Bracketed inline as unverified and pointed at the review record. Nothing ships until an attorney resolves it. |
| ·Not a citation claim | The sentence names no authority. There is nothing to check. | Recorded as such, so the reviewer knows no check was skipped. |
Treatment is a second, separate check: whether the authority is still good law for the use the draft makes of it. For load-bearing and first-use authorities the attorney runs it in the firm's own research account; the system hands off the citation and records the outcome and the attorney's confirmation. The system never logs into or scripts against a research service. Errors can still remain; review is part of the workflow.
Scope the workflows your firm needs. People retain judgment and approval.
Illustrative contract map. The blueprint fixes actual interfaces, controls and acceptance tests.
Approved inquiries organized and routed to the right owner. Missing details are flagged, not silently filled in.
First drafts follow approved templates and source material. You review the facts and flagged uncertainty.
Source checks surface missing or mismatched support. Reviewers resolve exceptions; errors can still remain.
Approved meeting records become draft notes and action items. Unmatched records wait for review.
Approved corrections update your private playbooks and templates. They do not train a model.
Reminders and queued updates support follow-through. Client-facing sends need approval; optional care supports the existing systems within agreed hours.
| System | Input → Output | Gate / exception | Evidence |
|---|---|---|---|
| 01 · Intake & Routing | Approved inquiry → structured record and proposed owner | Required inputs/consent missing or route unmatched → hold for review. Assignment confirmed before client contact. | Routing cases; refusal log |
| 02 · Document Production | Approved template + record → draft | Unsupported facts stay flagged. Current content and recipient need approval before release. | Fixture draft; approval record |
| 03 · Verification Gates | Claims/citations → source-check report | Missing or mismatched support → flag for review. Checks do not certify accuracy. | Source/quote trace; exceptions |
| 04 · Meeting Intelligence | Consent-documented record → draft notes/actions | No consent or matter match → hold. Reviewer confirms filing. | Consent/match cases; note log |
| 05 · Knowledge Layer | Approved correction → updated guidance | Only accepted updates enter guidance; client/matter access stays isolated. | Change log; access tests |
| 06 · Follow-Through | Deadlines + threads → reminders/queued updates | Expired review → internal reminder only. No approval → no client send. | Pending/cancelled cases; send log |
Work directly with the founder. Send care requests anytime. Routine requests receive a response within one business day. Business hours: Monday-Friday, 9 a.m.-6 p.m. Eastern Time (America/New_York), excluding U.S. federal holidays. System-blocking incidents take priority, with best-effort assistance outside business hours. A response acknowledges the issue and establishes the next step; it is not a resolution deadline. Resolution depends on the issue and any upstream provider. This is not a 24/7 staffing guarantee. Included care hours and prior written approval for additional work still apply.
Care uses the same agreed hours and response policy. Full care terms →
Illustrations only, not client results or guaranteed integrations.
Scattered client details create repeated entry. A scoped workflow could organize approved intake, summarize the kickoff and queue missing-item follow-ups for professional review. Tool access and firm standards are checked before a build is recommended.
No tax-system compatibility or autonomous accounting judgment is claimed.
Discovery notes become another manual proposal. A scoped workflow could organize approved notes, draft from the firm’s proposal structure and surface next steps for review. Scope, pricing and client commitments remain with the firm.
No measured savings, completed engagement or supported connector is implied.
Your highest-paid people are doing administrative work. The audit maps the work still done by hand after current tools, estimates recoverable capacity, and recommends a band. Capacity is not cash savings or guaranteed revenue. The audit scopes the price; the price scopes the build; the build scopes the modules. You choose the build, and it is fixed in writing before work begins.
method: the audit maps remaining manual work and estimates recoverable capacity at your own rates · the larger the figure, the larger the band the audit recommends · you choose the band you build · fixed price, in writing, before work begins · no hourly meter on the build · no SF per-seat fees · bands are defined scope, not packages · acceptance criteria written into the blueprint before signing · final payment due only after the system passes them
Billable-practice model: value residual manual work after current tools at your loaded admin rate. Do not count an hour twice.
Your suggested band already includes a set of systems, document types, integrations, and jurisdictions. Add more here and the price adds at the published module prices.
Method: residual manual hours × 75% assumed recovery × loaded rate × 50 working weeks = modeled annual recoverable capacity value. The audit checks your inputs against your records and estimates recovery system by system; it does not turn a forecast into measured results. It recommends a band and price; you choose the build, and the blueprint fixes scope and price before signing. Minimum engagement: $12,000. Modules follow the build at published catalog prices. Optional care: $750, $1,000, or $1,500 per month with 3, 5, or 8 included hours; additional hours $250/hr with prior approval. The build is a one-time fee. Synapse Forge’s ongoing care plan is optional. Existing software subscriptions and any cloud or usage charges are separate; the blueprint lists the costs that apply to your build.
Modeled scenario, not measured outperformance or total operating cost. Enter residual manual work after current tools, with no overlapping hours; those tools may already deliver benefits. Capacity value is not cash saved, profit, or guaranteed billing. Year-one and annual capacity rows exclude care and operating costs. Subscription line: modeled recoverable capacity value plus the entered platform bill. Build line: build and modules plus displayed optional care, assuming that platform is retired. Both exclude remaining 25% manual work and unknown software, cloud, inference, and processing charges; exclusions are not zero. Break-even uses capacity value plus assumed platform charges avoided, less care, not cash payback. Negative year-one and five-year differences display as zero. Ending care does not cancel vendor bills.
Up to three systems, three launch document types, two integrations, one jurisdiction, two named reviewers. A focused core against your sharpest bottleneck.
Price set by your audit · $12,000 minimumOptional care at this scope: $750/mo · 3 hrsUp to five systems, five document types, three integrations, two jurisdictions, three named reviewers. The extended build, wired together so work moves from intake to follow-through.
Price set by your audit · fixed in writingOptional care at this scope: $1,000/mo · 5 hrsAll six systems, six to ten document types, three to five integrations, three or more jurisdictions, four or more named reviewers. The full operating system.
Price set by your audit · fixed in writingOptional care at this scope: $1,500/mo · 8 hrsThe audit recommends a band and the blueprint lists exactly what is in; you choose the band you build, fixed in writing before you sign. Each band is a defined scope, so a larger band is always a larger build, and the build sets which modules you can add later. Every band includes the scoped configurations, workflows, prompts, operating docs/runbook, and access-control ownership. License and provider costs continue if care ends. Full detail on Pricing.
Everyone else: the audit is free, specific to your firm, and yours to keep either way. Request it below.
A focused 30-minute conversation. Same-day written findings. Your report arrives the same business day once the call and any agreed outstanding inputs are complete. No obligation to build. Send your contact details and a brief workflow description; we reply to arrange the call. You receive a written systems recommendation and, if a build fits, a recommended band and price. The initial reply is not the completed audit.
Have your current tool list, team size, and top two repetitive workflows ready. Estimator results are helpful, not required. We confirm any missing inputs at the end of the call. Timing uses Eastern Time and business days, Monday-Friday excluding U.S. federal holidays. If both requirements are completed on a non-business day, delivery is the next business day.
For technical reviewers. Ask for the Data Boundary Sheet template with your audit: the one-page record of where data lives, what is verified before activation, who can access it, and what happens when the relationship ends. Thirty minutes. You leave knowing what you would have to verify. Read the architecture boundary summary first if you want the design in general terms.
You'll work directly with Matthew Samlal, the founder of Synapse Forge. No account managers, no handoffs.
Use the existing sample and estimator first. If useful, copy this draft and replace [our workflow] before sharing it internally.
Nothing is sent automatically. Select the text and copy it yourself.
Three scope bands, one fixed build price: Spark up to three systems, Forge up to five, Foundry all six. The free Systems Audit recommends a band and price; you choose the build. The blueprint fixes scope and price before signing, with no re-pricing after. The audit scopes the price, the price scopes the build, and the build scopes the modules. Minimum engagement: $12,000. Payments fall at signing, mid-build demonstration, and written acceptance. After acceptance, add modules at published prices. Optional month-to-month care after acceptance: $750/3 hours, $1,000/5 hours, or $1,500/8 hours per month; extra hours $250/hr with prior approval. The build is a one-time fee. Synapse Forge’s ongoing care plan is optional. Existing software subscriptions and any cloud or usage charges are separate; the blueprint lists the costs that apply to your build.
We reduce these risks with grounded drafts, source and quotation checks, deterministic rules, visible uncertainty, and human review before client delivery. Each agent has a defined job, limited permissions, and an audit trail. Errors can still remain. Development and regression testing use synthetic fixtures; operational activation requires written agreement and client permissions. No client content leaves the client project for testing, evaluation, monitoring, or diagnostics. The Data Boundary Sheet documents approved processing flows and sign-off; actual provider, region, retention, and training terms must be verified before use. Synapse Forge does not pool, resell, or use client data for model training. The design supports the firm’s confidentiality obligations; it does not certify compliance or preserve privilege by itself.
The build targets residual manual work such as intake re-keying, meeting filing, status chasing, and draft re-checking. Recovered time is capacity, not cash savings, profit, or guaranteed billings. Drafting time may be billable today. Flat-fee firms may use recovered time to reduce effort per matter; hourly firms need suitable work to redeploy it. The audit separates billable and nonbillable work, checks what current tools already handle, and estimates recovery at your rates so you can judge the trade-off. It augments the team rather than replacing professional judgment.
No archive cleanup is required. The build uses a curated launch set of live templates, current playbooks, and agreed documents. We structure that set inside the build scope; choosing standards and resolving template disagreements stays with your firm. The Pre-Build Readiness Checklist itemizes access, templates, reviewers, responsible owners, and time estimates. Hands-on person-hours and elapsed approval time are different; preparation depends on permissions and readiness. The 4–6 week build runs from kickoff, not inquiry or signing alone. Kickoff is the next business day after the agreement is signed, the signing payment has cleared, the checklist is complete, and access is verified. Signing payment does not authorize operational activation before the agreed consent scope.
The audit starts with a focused 30-minute conversation. Your report arrives the same business day once the call and any agreed outstanding inputs are complete. No obligation to build. The report shows what we recommend before you commit. The blueprint puts scope, price, and acceptance criteria in writing; final payment is due only after the system passes the agreed criteria. Every band includes the scoped configurations, workflows, prompts, and operating docs/runbook with access-control ownership. The Work section shows synthetic examples of the deliverable formats, not customer outcomes or executed real-matter acceptance tests. Judge the proposed scope and criteria before deciding.
More answers on How It Works and Pricing.