Honest answers about hiring Leif.

It does not reach the client. Leif drafts, you approve. Nothing client-facing leaves your business without your two-tap approve. If a draft is off, you edit and approve, and that correction trains the next round. The Maplewood paver estimate, the Henderson COI renewal note, the Friday client memo: all of it queues for you first.

The five inputs Leif checks before drafting (sources, prior approvals, voice rules, calendar context, customer history) are visible in the work record for every draft. You can see why Leif wrote what it wrote, and you can correct the upstream input once instead of re-fixing the same mistake every week.

A custom GPT is a prompt you re-paste every time. Leif is a server-side employee with persistent memory, scheduled actions, OAuth (Open Authorization) integrated tools, owner approval on every external send, and an audit ledger. Leif logs in once and stays logged in. Leif reads the Maplewood paver thread on its own, drafts the reply, and waits for your two-tap approve.

Leif owns the loop; you own the approval. ChatGPT helps for a week. Leif gets sharper the longer it runs against your real work, because every approval and edit you make is remembered, and the next draft starts from a closer copy of your firm voice.

An agency custom AI build quotes 60 to 90 days and $25,000 to $100,000, then leaves you with a system you have to maintain. Leif is a hand-delivered employee, shipped in one week, at $500 per seat per month base or $2,500 per seat per month with Tavus voice and face employee.

No SOW. No scope creep. No implementation phase. No hand-off. The Leif team owns the build and keeps owning it; you own the approvals.

Three real ones. (1) You give Leif OAuth access to your inbox and CRM so it can read prior threads and draft from them; revoke any time and Leif loses access the moment the token is gone. (2) Your client information lives in our system. We do not share it across customers, but it is there; the security setup (per-customer database isolation, encryption at rest, audit log on every action) is documented on the FAQ. (3) The trained employee belongs to your account; if you cancel, your data exports the same week, and the model that learned your voice does not come with you.

The other thing some people call a catch but is really how we work: one new client per month by design (capacity cap, not scarcity marketing), and you are the editor in the first week so Leif learns your approvals.

Greater Boston. We work with operators in the Merrimack Valley, Southern New Hampshire, and across the Boston metro. In-person kickoff is available if you are local; remote kickoff if you are not. We drive to your office for the Day 1 meet inside a one-hour radius. Outside that radius, kickoff runs on video and the timeline is identical.

The product is the same. The proximity is a feature, not a constraint.

Approval is the default. Everything client-facing waits for your two-tap approve. Nothing posts to the client, the CRM, or the accounting tool without you saying yes. A reply to a Bridge Lane homeowner, a quote send, a Stripe invoice, a calendar invite, a memo to a CPA client: all of it queues for you.

Wider permissions are an explicit owner decision, not a setting Leif flips on its own. Some operators eventually auto-approve a narrow band (status replies, internal-team Slack updates, calendar-confirmation messages) once they trust the pattern. That is your call and it is per-workflow.

It flags it. Leif names the uncertain piece, proposes the verification step, and waits for your call. A real example: `I am not sure the Henderson COI expires Friday, want me to call the carrier?` beats a confident guess.

Stuck items show up in the Today view as a separate column so you see them in 10 seconds. You answer once and Leif writes the answer to memory so the same question does not come back next week.

Yes. Leif reads your inbox, your CRM, your filings, your calendar, your prior approvals, and your voice corrections. Every approve and edit retrains the next draft, so the work lands closer to ship-ready as Leif learns your voice.

The training is not a one-time setup. Each edit you make sharpens the next draft. Your firm's playbook becomes Leif's playbook.

No. You do not train it. We do. Leif arrives pre-trained on your business by the time you sign in, with your inbox patterns, your CRM records, your prior correspondence, and your voice rules already loaded. The first week of approvals tunes the voice. After that, every edit you make sharpens the next draft.

You are reviewing drafts in plain English, not writing prompts.

Day 1 we meet and pick the first workflow. Day 2 and 3 we connect your project folder, templates, examples, and approval rules. Day 4 Leif drafts into your review queue. By Day 7 the queue is running and your edits are training the next round.

Expect to spend 30 to 45 minutes a day approving drafts in week one. As the voice settles on your corrections, that time drops. You do not install anything. You do not configure anything. We deliver Leif pre-trained.

Only what you connect. Email, CRM, calendar, accounting, Stripe, whatever you OAuth-grant (OAuth = Open Authorization). Read-only by default. Leif never sends, charges, or modifies anything outside your business without your explicit two-tap approve. You can revoke any connection from the integrations page in one click, and Leif loses access the moment the token is gone.

Per-tenant encryption at rest. Row-Level Security (RLS) on every tenant table, so your data is isolated from every other operator's data at the database layer. No cross-tenant exposure.

Yes. Your data is isolated per customer in a Row-Level-Security-enforced database, encrypted at rest. Connection tokens stay server-side; nothing sensitive is shipped to the browser. Every external send waits for your approval. Every Leif action lands in an audit log you can read. Your customer's data lives in its own row and never touches another firm's data at the database layer.

For tax-practice surfaces, Leif is built to follow IRS Publication 4557 data-security guidelines and supports your firm's Written Information Security Program (WISP); the written WISP template is available on request. No PII (Personally Identifiable Information) sent over insecure channels. The Leif team walks you through the exact configuration on Day 1, including which connections to enable and which to leave off.

Yes. Cancel any month, no questions. It is month to month: a one-line email stops the next invoice, and your data exports the same week.

No annual lock-in. No cancellation fee. Annual prepay terms are available on request.

The premium tier ($2,500 per seat per month) adds a Tavus replica: a voice and face employee your customers can see and hear. Same employee, same owner approval before anything sends, same training. The only difference is the voice and video interface customers see and hear.

Use it for the calls and explainers where presence matters (a client kickoff, a quote walkthrough, a renewal call). Use the base tier for everything else. You can turn the premium tier on for a single seat and leave the rest on base.

Run the math against your own rate. At your billable rate, even 5 hours a week back is well above $500. The question is whether the hours are real. Leif is month to month, so if it is not earning its seat you cancel with one email, no contract holding you.

The shape that gets the most back: an owner who currently spends evenings on email, organizer chase, COI follow-up, or after-hours quote replies. If that is your week, the hours come back fast. If they do not, you cancel any month, no contract.

Leif works with your existing tools, not against them. OAuth-connect (OAuth = Open Authorization) what you already use. Leif drafts in front of those tools and never replaces them. The portal stays. The CRM stays. The accounting tool stays. You keep your TaxDome organizer, your Jobber dispatch, your HubSpot pipeline, your QuickBooks ledger.

Leif is the operator inside your stack: it reads the QuickBooks ledger to draft the client memo, reads HubSpot to draft the follow-up, reads TaxDome to draft the organizer-gap email. You approve, and the action posts back to the tool of record.

No. Leif takes the repeatable analyst, associate, business-development, and review work off the people you already have. Their hours move to judgment work and client relationships. A junior who used to spend 12 hours a week chasing organizer gaps now spends those 12 hours in advisory calls. Same team, higher-value work.

The shape that works: Leif drafts and follows up. A part-time admin handles the human-touch calls and the physical-world tasks. The owner reviews and approves.

Leif is not a fit when there is no repeatable workflow to start with, no owner around to review the first weeks of drafts, or no real cost to slow follow-up. A pure one-off bespoke shop with zero recurring artifacts gives Leif nothing to learn from, and a firm where nobody can spend 30 minutes a day approving in week one will never tune the voice.

The 30-minute intake call is the place to find that out.

Yes. Leif handles IRS notice triage, organizer-gap chase emails, prior-year return requests, W-9 collection, quarterly estimate reminders, and client follow-up. Senior-grade reviewer output stays inside your CPA sign-off chain. Nothing files. Nothing posts. Every draft waits for your two-tap approve before it reaches the client or the practice management system.

A typical CPA pilot in busy season looks like this: Leif drafts the organizer-gap email at 6:30 AM, you approve at 7 AM with coffee, the email is in the client's inbox before the day starts. The hours you used to spend chasing missing items shift to tapping approve.

Yes. Most home-service inbounds land after hours. A 2011 MIT study on lead response (Oldroyd, McElheran, Elkington) found that response speed dramatically increases the odds of qualifying the lead, and the dynamic has only sharpened in the fifteen years since. Leif drafts the first reply inside one minute; you approve from your phone in two taps.

A typical contractor workflow looks like this: the porch-quote request hits your inbox at 8:14 PM. Leif drafts a reply naming the address, the scope, and three available walkthrough windows. You tap approve. The lead is booked before your competition reads the email.

No. Solo operators are where Leif earns its keep fastest because every hour back is your hour. Leif drafts client memos, books the calendar, chases missing documents, and writes the Monday status note while you do the work only you can do.

The shape that works for a solo: start on a single workflow (intake, follow-up, or weekly client recap), add a second once the first is humming. You pay for one seat, not a per-message charge.

Yes. Each client lives in its own context with its own files, voice rules, approved language, and prior corrections. Leif does not mix Client A's drafts with Client B's, and the memory layer is scoped per client. A Henderson family office memo never borrows tone from a Maplewood paver thread. Switch clients in the sidebar and the entire context follows.

The shape that works for an agency: start with the highest-volume client account, prove the pattern, then add the next account. One seat covers your whole book; you do not pay per client.