Scaleso
How We Work

Designed per engagement, structured per project.

Every scaleso engagement starts with a free diagnostic and ends with a verified outcome. Pick the layers you need below — your selections feed the assessment that determines scope, timeline, and pricing model.

Pick what you need

Which layers do you want to engage scaleso for?

Pick any combination. We'll route your selection into the assessment.

L6

Incident response

What happens when something breaks — playbooks, on-call, post-mortems, damage control. The defense layer.

Connects to: Triggered by monitoring, draws on every other layer

L5

SEO for AI

How Claude, ChatGPT, and Perplexity decide whether to cite you. Distinct from traditional SEO and increasingly decisive.

Connects to: Citation layer that sits on top of traditional SEO

L4

Traditional SEO

How humans still find you — technical SEO, schema markup, content architecture, ranking discipline.

Connects to: Visibility layer powered by app structure and content

L3

Business automations

The operational glue — workflows, integrations, internal tools that run the business that runs the app.

Connects to: Sits between the app and the operations behind it

L2

Application & marketplaces

The visible product — full-stack web apps, marketplaces, dashboards. Hand-coded, fast, accessible, observable.

Connects to: Surface that automation drives and SEO points to

L1

Security & monitoring

Headers, secrets, dependency hygiene, SSL grade, real-time monitoring. The base every other layer sits on.

Connects to: Foundation for app, automation, and incident response

Pick at least one layer to continue.

Engagement Methodology

How a scaleso engagement actually runs.

Every engagement is custom, but the spine is the same — seven stages, weekly visibility, kill-switches you can use.

01
Day 0 · 10 min

Free diagnostic assessment

You submit the assessment. We scan your current site and surface concrete findings before any sales conversation.

What we do

  • ·Process your interactive assessment submission
  • ·Run automated scans: performance, security headers, SEO baseline, AI-citation readiness
  • ·Map findings against scaleso's six service layers

What you see

  • ·Diagnostic snapshot with named issues, not generic advice
  • ·A recommended engagement track and indicative time/cost band
  • ·A booking link for the diagnostic call — only if there is a fit
GateYou decide whether to book the diagnostic call. No commitment, no follow-up pressure.
02
Week 0–1 · 3–5 days

Engagement design

The single most important artifact in the engagement. We write down exactly what we are delivering, by when, and on what terms.

What we do

  • ·Author the engagement document: scope, success metric, milestones, deliverables
  • ·Choose pricing model: retainer, retainer + bonus, or fixed-outcome
  • ·Define risk allocation, kill-switch terms, weekly cadence, and acceptance criteria

What you see

  • ·Signed engagement document covering everything above
  • ·Written guarantee terms and refund triggers, in your jurisdiction's language
  • ·Kickoff date and weekly demo schedule
GateMutual signature. From this moment you have a 30-day no-questions-asked exit.
03
Week 1–2

Foundation sprint

Before we build features, we build a foundation that will not have to be rewritten in six months.

What we do

  • ·Architecture decisions, security baseline, secrets management, monitoring hooks
  • ·Set up staging and production environments, CI, observability
  • ·Document every load-bearing decision in a public decision log

What you see

  • ·Working staging URL with the skeleton in place
  • ·Live monitoring dashboard you can read
  • ·Decision log explaining every architectural choice
GateFoundation sign-off. We do not start feature work until you approve the base.
04
Weeks 2 → end · weekly cadence

Build sprints

We ship one shippable increment per week. You see, test, and redirect every Friday.

What we do

  • ·Implement scope in weekly increments against the engagement design
  • ·Run a Friday demo, capture decisions, file change requests on the spot
  • ·Track hours spent vs. budget and publish the running total

What you see

  • ·Working staging environment that updates continuously
  • ·Weekly demo recording, written progress note, hours-burned report
  • ·A direct change-request channel — no ticket queue
GateEvery Friday: continue, redirect, pause, or use the kill-switch. Your call.
05
Final week

Hardening & verification

Everything we shipped is verified against a published quality bar — not against our own marketing copy.

What we do

  • ·Full Lighthouse, security headers, accessibility, and load-test pass
  • ·AI-citation readiness check (schema, structured answers, source markup)
  • ·Measure the outcome metric agreed in stage 2, with raw data

What you see

  • ·Verification report scored against scaleso's published quality bar
  • ·Outcome metric snapshot: target vs. delivered
  • ·Performance bonus calculation, if applicable, with the math shown
GateOutcome metric measured against engagement-design target. Bonus released or refused on the data.
06
Final 2–3 days

Handoff & training

You leave the engagement able to operate the system without us — even if you choose not to.

What we do

  • ·Write the operating manual and incident runbook
  • ·Run a recorded training session for your team
  • ·Transfer monitoring, secrets, and ownership of every artifact

What you see

  • ·Operating manual, runbook, and recorded training in your hands
  • ·Every dashboard transferred to your accounts
  • ·Final acceptance document and billing reconciliation
GateHandoff acceptance. The engagement is closed.
07
Optional · month-to-monthOptional

Ongoing care

If you want us to stay on the system, we do — under a separate retainer with the same exit terms.

What we do

  • ·Incident response on-call within agreed SLA
  • ·Monthly drift review across performance, security, SEO, and AI-citation
  • ·Quarterly strategy review against your evolving outcome metrics

What you see

  • ·Monthly status report and drift dashboard
  • ·Incident SLA you can quote in board meetings
  • ·Quarterly outcome review with adjustment recommendations
GateMonth-to-month. Cancel any month, for any reason.

From the signed engagement design (stage 2) you have a 30-day kill-switch, no questions asked. Any performance bonus is calculated against the outcome metric agreed in stage 2 and verified in stage 5.

Quality bar

Every engagement ships verified against this bar.

Non-negotiables on every project. Measured in the hardening stage. We refuse handoff until they pass.

≥ 95

Lighthouse Performance

A+

Mozilla Observatory grade

Hardened

OWASP Top 10

WCAG 2.2 AA

Accessibility

From day 1

Monitoring & uptime alerts

Documented

Source-controlled handoff

Risk reversal

Written guarantee terms in every engagement.

30-day kill-switch from contract signature. Refund triggers tied to the outcome metric agreed in stage 2 and verified in stage 5. Performance bonus calculated on measured data — released or refused on the numbers, not opinions.

Read the guarantee terms

Start with a free diagnostic.

Submit the assessment. We scan your current site and send back a snapshot with concrete findings — no sales call required.

Start free assessment