Help and answers

Discovery inside a week of the first call, work starting the week after in most cases.

No. We own the operating layer and work with the people you already have.

A COO search takes six months. This is senior operations capacity inside two weeks, scoped to the problems in front of you.

Engagements are scoped by outcomes, not hours: a defined set of workflows owned, a delivery cadence, and one monthly number.

Not for most of it. Many use cases ship on tools your team already has.

We work inside your accounts and set retention and access rules as part of the engagement.

Then the assessment says so and we tell you where to spend the money instead.

We are vendor independent. The tool gets chosen after the process is understood, per task, and gets replaced without drama when something better ships.

That is usually one of the findings. The plan includes the minimum cleanup that unlocks the first use case, not a two-year data project before anything useful happens.

Technical gains show in weeks. Competitive terms take two to six months of consistent publishing.

Yes, and we run it past you before it publishes.

No one honest does. We guarantee the work, the monthly reporting, and that every page targets a search that verifiably exists.

Yours. We draft, you approve, and the voice guide is written with you up front.

LinkedIn and X by default. Others when they fit the audience.

Yes. Engagements run month to month after the first term.

We do, in a voice guide built from your own words in the first two weeks. You approve from your phone; nothing publishes without a yes until you tell us otherwise.

LinkedIn and X are the core for B2B. Others are added only when your buyers are demonstrably there, not because the platform exists.

Yes, and it usually lowers their bill.

Yes. Scope and price depend on the jurisdictions involved.

No, and we do not give legal advice. We run the operations around your counsel: the calendar, the documents, the filings, the follow-through.

The deadline calendar: every filing, renewal, and registration in one place with owners and dates. Visibility first, then the backlog gets worked down.

No. They file and advise; we keep the books they file from, which usually lowers their bill.

Less than leaving it, in almost every case. The figure follows a short call, because it turns on how many months are open. The tool on the service page counts what the delay already costs, from your own figures.

Yes. Bank statements in, month by month, until the balances tie. A project with a date, then a weekly rhythm.

A set business day, the same every month, with the reconciliations and reviewed statements behind it.

Yours. QuickBooks Online, Xero or NetSuite, in your account under your login.

No. We commit to the pitching work and report exactly what came back.

It ranges enormously by market and screen. We price the campaign work and quote placements separately.

Yes, artwork and production are included in the campaign quote.

We pitch where the story fits, which is what gets replies. Target lists are agreed up front; guarantees of specific outlets are a sign someone is selling ad space.

It varies by market and format. One engagement covers placement strategy, creative, and the negotiated buy.

Most sites go live in two to four weeks from the first call. Larger builds get a dated plan inside the written quote.

Whatever the job needs: static builds for speed and search, or a CMS when you will edit content often. Either way you own the code and the accounts, with no lock-in.

Yes. Redesigns keep your URLs and search history intact, so rankings carry over instead of resetting.

Cross-platform first: one codebase for iPhone and Android keeps cost and update speed sane. Fully native only when the app truly needs it, and we will say so plainly.

Yours. Apple and Google accounts are opened in your name, so the app, its users, and its reviews always belong to you.

Submission, rejections, and resubmissions are handled as part of the build. Review surprises are normal and planned for in the schedule.

Both, from one codebase, unless there is a strong reason not to. React Native builds ship to the App Store and Play Store from the same code.

You do: your Apple and Google developer accounts, your repository, your keys. Everything is transferred and documented; nothing is held hostage.

Both, in that order. The assessment names the leaks with numbers attached; the same team then builds the fix. No deck that dies in a drawer.

No. The assessment often finds that process fixes and simple automation come first. AI is applied where it adds value, not everywhere it fits a slide.

Mid-market companies past the founder-does-everything stage: enough moving parts to leak value, enough scale for the fixes to pay back fast.

First findings arrive in writing within two weeks: where the leaks are, what they cost, and what we would fix first. The first build lands inside the first month on most engagements.

Engagements run monthly, scoped and priced up front. Everything we build is documented and owned by you.

A senior operations lead runs the engagement, with specialists brought in per task: writers, engineers, filers, media buyers. You deal with one point of contact and one quote.

No. Remote recording is fine and we handle the setup.

Fortnightly is realistic for most companies and beats a weekly show that stops after six episodes.

About the recording hour, plus a few minutes of async approvals. Prep briefs, guest handling, and everything after the recording are handled.

Yes: sourcing, outreach, scheduling, and a prep brief before every conversation, aimed at guests your buyers want to hear.

SEO is one source. This covers all of them plus what happens after the click.

Yes, when the maths works. Media spend is separate and passed through at cost.

Conversion fixes show within weeks. Traffic building takes months.

Whichever the math favors for your market. Paid buys speed, organic buys durability; most plans sequence paid first while organic compounds behind it.

Enough for a statistically honest test per channel. Below that threshold we say so and point the money where it works harder.

Yes, done carefully and compliantly. Reputation is the asset.

You do. We can also brief you before each one.

It depends entirely on the offer and market. We report from week one.

Booked, qualified conversations with context attached, not CSVs. A list you still have to work is our job half-done.

Against criteria agreed with you in week one: size, budget, need, timing. The criteria tighten as close-rate data comes back.

Yes, or clean up what you have if it is close.

Yes, or build a simple document identity if there is none.

Operationally yes, with your counsel reviewing anything binding.

Proposals, SOWs, contracts and terms, SOPs, handbooks, investor and board materials, and the templates that keep them consistent.

No. We produce attorney-ready drafts and run the operations around documents; your counsel signs off where legal judgment is required.

Usually yes. Remediation is quoted separately once we see the position.

No. We run the operations and coordinate with your counsel.

Yes. Scope and price depend on how many.

Annual reports, registered agent coordination, license renewals, state registrations, and the routine notices that keep entities in good standing.

Common, and fixable. We triage by penalty and exposure, file what stops the bleeding first, and work the rest down on a schedule you can see.

Usually it removes the worst part of jobs and moves people to better work.

It is documented, and we can stay on for support if you want that.

Whatever fits: native integrations, middleware like Zapier or Make, or custom scripts. Vendor independent, chosen per task, documented so you can maintain it.

One workflow, typically five to fifteen hours a week recovered, live inside the first month, with the before-and-after numbers in writing.

Most engagements run one to three weeks depending on depth.

Yes, and the document is built for that.

No. We produce research and analysis; decisions remain with you and your licensed advisors. Our work is the input, not the instruction.

A written brief: the thesis, the strongest case against it, the numbers checked against filings, and every claim cited to its source.

Usually not. Most clubs are missing attendance reporting and a working booking path, and both can be added around whatever is already in place.

Whatever the product cannot hold: a guest policy, a ladder, a family or corporate plan, a season, a waitlist that behaves the way your members expect.

Yes. Dues, guest rules, house accounts and events are the same shape of problem as memberships, bookings and classes.

Usually inside a month, because it points at members who are still paying and have not decided anything yet.

An automation follows steps you defined. An agent decides which steps to take, inside limits you set, and can handle input that varies. That flexibility is the point and it is also the cost.

Because it logs what it read, what it decided and why, and because the job was defined well enough that correct and incorrect are distinguishable. Both of those are design decisions made before anything is built.

It can misread an unusual case and act as though it were a normal one. The limits are what contain that: a narrow write scope, a value ceiling, a rule that anything outside a pattern goes to a person instead.

Whichever suits the job, and it is a decision worth making on evidence rather than on brand. Some jobs want the strongest reasoning available and some run happily on something small and fast.

Those answer from a list of canned replies or from a general model with no knowledge of your business. Useful for opening hours, thin for anything else.

It says so, takes the details, and hands over. That behavior is designed in rather than hoped for.

Yes, and whether it should is worth a conversation first. Booking works well when the next step is a calendar slot.

Weeks rather than months for a first version you can put in front of people, and it improves from real conversations after that.

Claude, GPT, Gemini, Grok, Copilot and Perplexity by default, the current version of each. Any model with an interface can be added, including open models you host yourself.

Whatever the decision depends on. The usual set is accuracy on your material, whether the answer cites a source you can check, whether the same question gets the same answer twice, how it handles your files, speed, and cost at your volume.

Your questions and documents are used for the test and nothing else. Where a model offers a no-training setting, it is on. Sensitive material can be masked or replaced with matched samples before it goes anywhere.

Public benchmarks score models on public tests, which the models have often seen. They say nothing about your contracts, your tickets or your tone.

Usually the opposite. Most companies already own more capability than they use, and the gap is between the tools rather than inside them.

Whichever one the work naturally starts in, and whichever one people already trust when the two disagree.

Some of them are the problem and some of them are the documentation. Worth telling apart before deleting anything.

The measurement takes about two weeks and produces numbers you can act on with or without us. The first connection usually follows within a few weeks of that.

Because the problem is usually upstream of the dashboard. If two people define the same metric differently, no amount of charting fixes it, and the screen becomes something people argue with rather than act on.

Whatever you already have, wherever that is honest. Sheets and Looker Studio go a long way and cost nothing. Airtable, Metabase, Power BI and the reporting already built into your CRM or finance system are all fine.

The definitions and the question list come out of the first week, and they are usually the first time anyone has seen the business described that way.

It is the normal starting condition and it is not a reason to wait. Messy usually means duplicates, missing fields and three conventions for the same thing, all of which are visible once you look.

No. This is systems and operations: access, change, vendors and backups. A financial audit looks at the books and needs an accountant. Neither one covers the other.

A week where there are a handful of systems, longer where nobody has a full list of what is running. Most of that time goes into assembling the inventory, which is why the second round is much faster than the first.

Access quarterly, because leavers and role changes happen continuously. Vendors and backups twice a year. Change control is continuous by nature, and the audit is a read on whether the record was kept.

A spreadsheet is fine for the first two rounds and it is the right answer for most companies this size. Buy a tool once the list of systems is long enough that maintaining the spreadsheet is itself the work.

Possibly not. Worth spending two minutes on the checker above before deciding, because the question is not whether the site is up.

Yes, and it is most of this work. We start by finding out what it is built on, which is occasionally a surprise to everyone.

Common, and recoverable more often than people expect. Domain ownership is provable, hosting accounts have recovery paths, and registrars have a process for exactly this.

Monthly for the checks that matter, and immediately for a security fix that is being actively exploited.