ark — scope of work
The catalogue, in numbers
- 15Discrete serviceseach one a line you can strike
- 4Clusters, each standalonestart with one, layer the rest
- 7-30dTypical build windowbuild time, not time to results
Services
Built to a list.Priced against it.
Four clusters, 15 discrete services. Every engagement is scoped against a written deliverable list, so you can see what you are paying for and stop at any line. Most clients start with one cluster and layer the rest as the operation opens up.
An illustration of the catalogue: 15 discrete services across four standalone clusters, built in seven to thirty days, documented rather than merely delivered, with admin access in your names and a runbook your team can follow.
The clusters
Four clusters.Each one stands alone.
Point at a cluster to read it
Live in 7 to 14 days
Everywhere a buyer meets you before they meet a person.
The site, the CRM, the voice agent, the chat, the search surface and the editorial behind them. Five layers a prospect touches on the way to a conversation, and the five most people leave to chance.
- Pages built against the buying decision, not a template
- Stages with a clock, and a dormant list worked properly
- Voice and chat agents wired into the pipeline
Live in 14 to 21 days
Every channel that puts a qualified buyer in front of you.
Paid, outbound and lifecycle, instrumented so you can tell which one produced the meeting. Run as one system rather than three agencies pointing at each other.
- Paid on Meta, Google and LinkedIn, measured end to end
- Cold outbound with replies parsed and routed
- Lifecycle email that works the list you already own
Live in 21 to 30 days
What runs underneath when standard software hits a wall.
Custom applications, multi-tenant platforms and the automation that joins a stack that was never designed to work together. Written to be handed on, not to be depended on.
- Internal tools, dashboards and field operations
- Multi-tenant platforms with isolated data per customer
- Automation across the tools you already pay for
Per engagement
The production layer. Finished pieces, not billed hours.
Long-form, short-form, social and paid creative. Cut, graded, captioned and delivered ready to publish, on a cadence the calendar can actually hold.
- Interview and podcast editing, start to master
- Vertical short-form cut for the platform, not resized for it
- Creative built for paid, not repurposed into it
The catalogue
Every line,open for inspection.
All fifteen, in full. Nothing is bundled, nothing sits behind a call, and no line depends on buying the one next to it.
01Frontline
Everywhere a buyer meets you before they meet a person.
The site, the CRM, the voice agent, the chat, the search surface and the editorial behind them. Five layers a prospect touches on the way to a conversation, and the five most people leave to chance.
01
Conversion Sites
10 to 14 days
Built page by page against the buying decision, not a template with your logo dropped into it.
- Multi-page builds your team can edit without coming back to us.
- Voice or chat handoff wired into the CRM at the point of intent.
- Marked up so search engines and answer engines can read the business, not guess at it.
- Fast enough to open on a phone with two bars in a car park.
02
Pipeline & CRM
7 to 10 days
One place a deal lives, with stages that mean something and a clock on every one of them.
- Stages defined by what has to be true, not by what feels tidy.
- Routing, ownership and reminders so nothing waits for someone to notice it.
- Reactivation across the dormant half of the database.
- Reporting that reads the same every week.
03
Voice & Chat Agents
7 days
An agent that answers, qualifies and books, then hands a human the context rather than a transcript.
- Answers on the first ring, day or night, in your language and your tone.
- Qualifies against your criteria and books straight into the calendar.
- Escalates to a person the moment the conversation earns it.
- Every call summarised into the CRM record, not left in a call log.
04
Search & AI Visibility
Ongoing, first pass in 14 days
Being found by the people searching, and being cited by the engines answering on their behalf.
- Keyword and question mapping against real volume, never estimates.
- Structured data so an answer engine can quote the business correctly.
- Technical work on the surfaces that actually gate ranking.
- Tracked as a hit rate over time, not promised as a position.
05
Editorial Desk
Ongoing
Writing that sounds like the person who runs the business, published on a cadence you can hold.
- Voice captured from what you have already written and said.
- Articles built around the questions buyers ask in the room.
- Published on your domain, on your schedule, with the internal links doing work.
- Every claim sourced before it ships.
02Demand
Every channel that puts a qualified buyer in front of you.
Paid, outbound and lifecycle, instrumented so you can tell which one produced the meeting. Run as one system rather than three agencies pointing at each other.
01
Paid Acquisition
14 days to first spend
Campaigns judged on booked meetings, with the tracking built before the first pound is spent.
- Creative written to pass the three-second test on a cold feed.
- Conversion tracking and offline events wired before launch, not after.
- Audience and placement structure that can be read a month later.
- Weekly read against cost per qualified meeting, not cost per click.
02
Cold Outbound
14 to 21 days
Email and LinkedIn to a list that was built, not bought, with deliverability treated as the first job.
- Domains, warm-up and sending infrastructure set up before volume.
- Lists built from a defined profile and verified before a send.
- Replies parsed, categorised and routed to an owner with a clock.
- Sequences that stop when a human takes over.
03
Lifecycle & Reactivation
10 to 14 days
The cheapest pipeline in the business is the list you already paid for.
- Nurture built around the objection, not the calendar.
- Win-back for closed-lost, segmented by why they went.
- Broadcasts that do not burn the list to hit a number.
- Held against reply and meeting rate, not opens.
03Machinery
What runs underneath when standard software hits a wall.
Custom applications, multi-tenant platforms and the automation that joins a stack that was never designed to work together. Written to be handed on, not to be depended on.
01
Internal Tools
21 to 30 days
The application your operation actually runs on, instead of the spreadsheet standing in for it.
- Built to the workflow you have, not the one a vendor assumed.
- Roles and permissions that match how the team really splits work.
- Runs on a phone where the work happens on a phone.
- Committed where your team can read it, from day one.
02
Platform Builds
Scoped per platform
Multi-tenant products where each customer's data has to stay genuinely theirs.
- Isolation enforced at the database, not in application code.
- Onboarding, billing and admin as first-class parts of the build.
- Audit trails on anything that touches money or a record.
- Documented so a second team can pick it up.
03
Workflow Automation
7 to 14 days
The connective tissue between the tools you already pay for, with alerts when a run fails.
- Every workflow monitored, with a named owner on failure.
- Idempotent writes, so a retry cannot duplicate a record.
- Credentials held outside the workflow, never in an export.
- The manual step is removed, not documented.
04Broadcast
The production layer. Finished pieces, not billed hours.
Long-form, short-form, social and paid creative. Cut, graded, captioned and delivered ready to publish, on a cadence the calendar can actually hold.
01
Interview & Podcast Edit
Per episode
Long-form conversations cut to the argument, with the dead air and the filler gone.
- Cut on meaning first, then on pace.
- Levelled audio, graded picture, captions burned or sidecar.
- Chapter markers and a written summary with the master.
- Delivered as a publishable file, not a project to finish.
02
Vertical Short-form
Batched monthly
Cut for the vertical feed from the start, rather than a landscape edit squeezed into a phone.
- Framed vertically at the edit, not cropped at export.
- Captions styled to be read with the sound off.
- Hooks written against the first two seconds.
- Batched, so a shoot day feeds a month.
04
Creative for Paid
Per campaign
Static and video built for a cold feed, where a viewer decides in three seconds.
- Who it is for, what the offer is, what happens next, all visible at a glance.
- One number and one window, both of which can be sourced.
- Variants built to isolate a single variable.
- Winners kept, the rest retired without ceremony.
How we work
Three rulesthat never get traded.
Day 0 to 3
Scope before build
The deliverable list, the access checklist and the delivery plan are settled in the first week. No discovery theatre, no scope drift, no second statement of work three weeks in.
Default posture
Automate by default
If a step happens every week and a machine can hold it, a machine holds it. Manual work is engineered out as part of the build, not sold back to you as an upgrade.
Week 1 onward
Measured, then changed
Every system reports against the same numbers each week. One change at a time, so the next week tells you something you can act on.
Do we have to take all four clusters?
No. Most engagements start with one, usually Frontline or Demand, and the rest gets layered on as the operation opens up. Each cluster stands on its own and each service inside it ships as a discrete unit.
Who owns what you build?
You do, outright. The code lives where your team can read it, the accounts carry your name, and the handover includes a runbook rather than a phone number. Nothing we build needs us in order to keep running.
What happens if we already have some of this?
Then we do not rebuild it. We audit what is there, say plainly what is working, and scope only the gap. Replacing a system that already earns its place is the easiest way to waste a quarter.
How is this priced?
Per service, against a written deliverable list, so you can see what you are paying for and stop at any line. Retained work is priced monthly against the same list.
How fast does something go live?
Frontline in seven to fourteen days, Demand in fourteen to twenty-one, Machinery in twenty-one to thirty. Broadcast is scoped per engagement. Those are build times, not the time it takes for a channel to produce.
Book a call
Pick a time.We bring the questions.
A short working session on the operation as it runs today. We find where the repeated work actually sits, name the part costing you most, and set out the order we would build in.
- No deck, no discovery theatre
- We name the constraint out loud
- The findings are yours whatever you decide
ark — book a working session
Step 1 of 2
Loading availabilityWeekdays
30 min · ET
Pick a day
That would be your slot
. This is a demo build, so nothing was sent and no details were stored.
Demo build, no live availability. To talk now: 305-513-1948 · info@arkadvisory.com
Free AI Assessment
Ready to builda system you can trust?
Tell us how the operation runs today and where the manual work is. If it is a fit, the next step is a working conversation, not a pitch.
- 305-513-1948
- info@arkadvisory.com
- Fort Lauderdale, Florida