Scope & Terms: Advisory

Last updated October 12, 2026.

Buying a website or local marketing? See Scope & Terms: Local Services.

These terms cover the advisory work inHaus & Co. sells: Architecture, and Operate in its two tiers. They are written to be read, not skimmed. If something here isn't clear, ask me before you sign.

The local services inHaus & Co. sells to Northwest Arkansas businesses are covered by a separate page, Scope & Terms: Local Services.

The agreement

This is an agreement between you, the business named in the proposal, and inHaus & Co. LLC, based in Rogers, Arkansas, and run by Hannah Craigen. You accept these terms by signing a proposal that links to them.

I lead every engagement today. There is no second operator.

What I sell

Architecture. $2,500 to $7,500, two to three weeks. Required first. Every engagement starts here.

Operate, one area. $5,000 a month. One team or process family, with one owner.

Operate, two areas. $7,500 a month. Two named areas of the business.

More than two areas is priced after Architecture.

Architecture is its own fee. There is no credit from Architecture toward Operate.

How an engagement starts

1. You sign the proposal.

2. A mutual NDA is signed. This happens before any work begins.

3. Architecture is invoiced and paid in full.

4. We hold a kickoff call: I confirm the scope, we schedule the interviews, and you tell me who your finance person is.

5. The interviews begin.

Work starts at the kickoff call. That matters for refunds, below.

Payments and billing

The monthly memo is sent with the invoice. The memo reports the month that just finished; the invoice covers the month ahead.

Operate has a three-month minimum, then runs month to month on 30 days' written notice.

Faster delivery than your tier allows, or training your own people to build workflows themselves, is quoted separately.

Prices are the ones published on the pricing page on the day you sign.

Refunds

Architecture. Refundable in full until the kickoff call. After that call, work has started, so it isn't.

If I decide I'm not the right fit. A full refund of anything paid for work I haven't delivered, whenever I work that out. If I can't do work worth what you're paying, I'm not keeping your money for finding out late.

Operate. Monthly fees already charged for a month that has started are not refunded. Give 30 days' notice before your next billing date and no further charges are made.

If I can't work. See "If I can't work," below.

What Architecture includes

I interview you and the people who run each part of the business. I time the processes that matter. I build the loaded-hour cost with your finance person, so the number is yours. I list every system and subscription you pay for, including the AI tools your staff already use.

You get:

• The areas of your business named in writing.
• The workflows inside each area, ranked, with a source on every row and a named owner.
• A written list of what I recommend against.
• A recommendation for which tier and which area to start with.

If the map says Operate will not pay for itself at your size, I tell you, and you keep the map. That is a real outcome of Architecture, not a failure of it.

Architecture does not commit either of us to Operate.

What Operate includes

Every month, in both tiers:

• Work on the next workflow in the queue.
• Fixes and upkeep on everything already built.
• Your AI use policy kept current.
• Tool and vendor decisions.
• A monthly memo, sent with the invoice.
• A quarter-end review you could hand to your bank.

The tiers differ in how much work is in progress at once. One area keeps one workflow in progress at a time. Two areas keeps two, one in each area.

The first 90 days

The first 90 days of Operate are the first Handoff.

• Weeks 1 and 2. The one-page AI use policy adopted, staff moved off personal AI accounts, the baseline for the first workflow agreed in writing, and the first build started.
• By week 3. The first workflow running in shadow mode. Your staff approve or edit every output before anything goes out.
• End of week 4. The first monthly memo: the baseline, what ran, and how many outputs needed edits. It does not claim hours saved yet.
• About week 6. The first workflow handed over. Your named owner is trained and passes the handoff test.
• Weeks 5 to 8. The second workflow scoped and built.
• By day 90. Two workflows delivered and measured, three memos sent, and a 90-day review that sets the next quarter.

This schedule depends on you. It starts when you have provided a named owner, access to the systems involved, and the baseline data. It pauses whenever any of those is missing. A pause does not pause billing once Operate has started.

How a workflow is finished

Every workflow goes through the same steps, and none of them is optional.

1. The scope. What starts it, what goes in, what comes out, where a person reviews it, the measured baseline, and a written definition of what working means.

2. The build. Tested against normal cases, missing information and the exceptions that break it, and checked by the people who will run it.

3. The governance minimum. A one-page AI use policy, a register of where AI is used, and a named checkpoint for the system.

4. The handoff. Training for your named owner. A runbook covering what it does, how to tell it is broken, who owns it and how to switch it off. Every account in your name.

5. The handoff test. Your named owner runs it while I watch and say nothing, then breaks it on purpose and restores it from the runbook alone. The date goes in the results memo.

6. The warranty. Below.

7. The results memo. Measured against the baseline we agreed in week one.

The warranty

Before each build, we agree in writing on a set of sample cases and the pass rate the workflow must hold.

For 90 days after the handoff test, if the workflow falls below that pass rate on those cases, I fix it at no charge.

The warranty ends if anyone other than me changes the workflow, its instructions or its connected tools.

While you are on Operate, upkeep is part of the fee anyway. The warranty is what you keep if you leave.

What I need from you

The work depends on a few things only you can provide. When one is missing, the related work waits, and waiting does not pause billing once Operate has started.

• A named owner for each workflow. No named owner, no workflow. A system nobody owns routes straight back to your desk, which is the problem you are paying to fix.
• Someone who can set priorities when a decision is needed between areas.
• Access to the systems the workflow touches.
• Baseline data. If the current process has never been measured, measuring it is part of week one, but I need the records to measure from.
• Your finance person, for a few hours during Architecture, to build the loaded-hour figure.
• Accurate answers. If something you told me turns out to be different, tell me. It may change what fits.

Communication and support

Support hours are Monday through Thursday, 9 a.m. to 5 p.m. Central.

I respond within one business day when a workflow is down, and within two business days for everything else.

There is no Friday, evening or weekend support. A workflow that breaks on Thursday evening gets a response on Monday.

Changes and requests go through email or the channel we agree on at kickoff, so there is a record.

What I don't promise

I don't guarantee a dollar figure, a percentage, a number of hours saved, or a result by a date. What I promise is the work described here, done well, on the schedule stated, and measured against the baseline we agreed in writing.

I don't promise that every workflow is worth building. Architecture exists to tell you which ones are, and sometimes the answer is fewer than you hoped.

I don't replace your ERP, your accounting software or your IT provider. I build inside the systems you already run. If a tool genuinely needs replacing, Architecture says so in writing before you spend anything.

I don't do formal regulatory compliance, SOC 2 evidence or enterprise governance programs. That is a different specialty and I will refer you.

Who owns what

You keep the instruction set, the knowledge base, the prompt library and every account. Everything I build lives in accounts in your business's name, from the first day.

You own your data, your content and your documentation.

The methods I use to deliver the work are mine and are not transferred.

I leave with nothing you need.

Data and confidentiality

A mutual NDA is signed before any work begins.

Everything I build lives in your accounts. I do not move your data into systems I control.

I do not use your business's data to train anything, and I do not reuse your documentation for another client.

I will not name you as a client in my marketing without your written permission. My work page describes clients by type of business and people by role, with no names.

If I can't work

If I cannot work for more than 10 business days, the engagement pauses or ends, at your choice, and the unearned part of that month is refunded.

Everything built is already in your accounts, with a runbook, and your named owner has been trained to run it. That is the point of the handoff test.

I lead every engagement today. There is no second operator, and I would rather say that here than have you find it out at a bad moment.

If the engagement goes quiet

During Architecture. If I don't hear from you for 30 days, I'll email you that it is paused. At 90 days I'll close it out and the fee stays spent. You can restart at the price in effect then.

During Operate. A quiet month is still a billed month. If the named owner or the access I need has been missing for 30 days, I'll write to you saying what is blocked and what it is costing, and either of us can end the engagement on the normal 30 days' notice.

Cancelling and ending the work

Operate. Three-month minimum. After that, 30 days' written notice before your next billing date. Nothing already charged for a started month is refunded.

What you keep when you leave. Everything built, in your accounts, with runbooks, plus the remaining warranty on any workflow whose handoff test is less than 90 days old.

If I end the work. I give you written notice and refund anything paid for work not delivered.

There is no exit fee and no transfer fee. Nothing needs migrating, because nothing was ever on my systems.

Late or failed payments

If an invoice is unpaid 7 days after it was due, work pauses until it's paid, and work resumes within two business days of payment. If it is still unpaid after 30 days, I may end the engagement.

Limit of liability

To the extent the law allows, the total liability of inHaus & Co. LLC for any claim arising from this work is limited to the fees you paid or owe for that work in the 12 months before the claim. Neither party is liable to the other for lost profits or indirect damages.

Governing law

These terms are governed by the laws of the State of Arkansas. Any dispute will be handled in the state or federal courts serving Benton County, Arkansas.

Changes to these terms

I may update these terms. Changes apply to engagements signed after the update date shown at the top. An existing engagement keeps the terms it was signed under until it ends or we agree otherwise in writing.