The packages
Package one · Introductory price
Workflow Starter
$1,200 USD
One-time, fixed-scope price · limited-time introductory offer
One important process, documented and ready for your team to use.
One process · up to two stakeholders · target completion within
one week once inputs and interviews are in place.
Package details ↓
Package two · Introductory price
Software Delivery Blueprint
$5,250 USD
One-time, fixed-scope price · limited-time introductory offer
Give one important software initiative a clear specification and a practical
implementation plan.
One initiative · up to five stakeholders and three systems · target
delivery three weeks after access and inputs are ready. A separate, larger engagement, not a required
upgrade.
Package details ↓
Introductory prices apply to engagements scoped while the offer is listed on this
page.
— ◈ —
Package one
Workflow Starter
$1,200 USD fixed price
Limited-time introductory price · one-time, fixed scope
One important process, documented and ready for your team to use.
When a process lives in one person's head, everyone else has to ask how it works. We help capture the steps,
responsibilities and decisions in a practical playbook, then test those instructions against a real example.
What you receive
- ✓
A discovery session with the owner and one key staff member.
- ✓
Review of a small, agreed set of existing materials for one recurring process.
- ✓
A concise playbook, typically 3–5 pages, covering steps, responsibilities, decision rules and a
reusable checklist or template.
- ✓
A walkthrough using one real example, one consolidated revision round and a handoff.
- ✓
A short recommendation on the next improvement or automation worth considering.
A good fit when
Your team repeats the same questions, a handoff is inconsistent, or important knowledge depends on one person.
Choose one bounded process, such as handling a new inquiry, preparing a project handoff or checking a
recurring deliverable.
Wiki Starter example
Use the engagement to create a small, useful wiki section for one process. We organize the content for an
existing suitable wiki or provide portable pages ready to import, and explain how to maintain them. A new
wiki platform is not included.
Scope and timing
One process, up to two stakeholders and an agreed source-material set. Target completion is within one week
after the required inputs and interview availability are in place. Delayed inputs or feedback may change the
schedule.
Custom software, integrations, data migration, platform deployment, subscriptions
and open-ended archive cleanup are outside this package. Additional processes or substantial scope changes
are quoted separately.
Discuss Workflow Starter
Tell us which recurring process you want to improve. We will confirm the scope
before the engagement begins.
Package two
Software Delivery Blueprint
$5,250 USD fixed price
Limited-time introductory price · one-time, fixed scope
Give one important software initiative a clear specification and a practical
implementation plan.
Before committing to a build or replacement, bring the business and technical stakeholders together. We help
clarify what needs to change, document the requirements and prepare the implementation team to move
forward.
What you receive
- ✓
Focused stakeholder interviews and a decision workshop to clarify goals, priorities and competing needs.
- ✓
A delivery brief covering current and proposed workflows, business rules, requirements, scope boundaries
and acceptance criteria.
- ✓
A prioritized implementation backlog and phased roadmap with dependencies, risks and an indicative budget
range. The range includes assumptions; it is not a fixed quote for development.
- ✓
One consolidated revision round and a guided handoff with your developer or vendor.
- ✓
One review of the developer's proposed implementation plan within 30 days of handoff, with a consolidated
list of corrections or questions.
A good fit when
A software initiative is stalled by unclear requirements, staff and developers have different expectations, or
an owner is carrying the entire coordination burden. The engagement focuses on one initiative rather than an
audit of the whole business.
Scope and timing
One agreed initiative, up to five stakeholders and three relevant systems, with one executive decision-maker.
Review uses agreed documentation and read-only access. Target delivery of the brief and handoff is three weeks
after access, inputs and stakeholder availability are ready; the plan review has its separate 30-day
window.
Production coding, migration, vendor procurement, exhaustive code or security audits,
subscriptions and ongoing project management are not included. Additional initiatives or major changes are
separately scoped.
You can use the deliverables with your own team or another implementation partner. Ongoing SGS delivery
leadership is optional and separately scoped.
— ◈ —
-
1. Confirm the fit
Describe the process or initiative. We agree the outcome, boundaries, required inputs and the person who
can make decisions.
-
2. Work through the details
We meet the relevant people, review the agreed material and turn it into practical documentation and a
plan.
-
3. Review and hand over
We walk through the deliverables, address one consolidated round of feedback and make ownership of any
open decisions clear.
Do these packages include software development?
No. Workflow Starter produces a usable process playbook. Software Delivery
Blueprint prepares a software initiative and includes a guided handoff and one implementation-plan review.
Building software or changing production systems requires a separate scope.
Do we need to buy more services afterwards?
No. You can use the deliverables internally or take them to another provider.
If you want SGS to guide implementation, we can scope that work separately.
What if we do not have a wiki or developer?
The Starter can be delivered as portable pages without installing a platform.
For Blueprint, tell us before booking if you do not have an implementer; we will agree the handoff
recipient and arrangements as part of scope. Finding or hiring a vendor is not included.
Are the timelines guaranteed?
The one-week and three-week timelines are targets that depend on access,
stakeholder availability and timely feedback. We agree readiness before starting and make delays or
unresolved decisions visible.
What happens when people disagree or the scope changes?
We work through competing needs with your designated decision-maker. Remaining
questions and disagreements are recorded with owners rather than hidden. A new process, initiative or major
change requires a separate scope; these packages do not include unlimited review cycles.
— ◈ —
An illustrative excerpt for a fictional business, showing the form of the
work. Real deliverables are written for your process and stay yours.
Workflow page
New client intake
Owner: Office manager · Reviewed quarterly
- Log the inquiry in the client tracker the same day.
- Run the conflict check before any call is booked.
- Send the intake form; chase once after two business days.
- Partner approves the engagement letter before work starts.
Decision rule: if the conflict check is unclear, stop and
escalate to the managing partner.
Decision log
Scheduling system replacement
- D-03 · Decided by owner
- Keep the existing billing system; the new scheduler syncs to it nightly rather than replacing it.
Why: billing works and staff trust it.
- D-04 · Open, owner: operations lead
- Whether clients can reschedule online without staff approval. Needed before the developer
estimates phase 2.
Acceptance checklist
Online booking, phase 1
- A booking made online appears in the staff calendar within one minute.
- Double-booking the same room is refused with a clear message.
- Every booking reaches billing in the nightly sync, with no manual re-entry.
- The office manager can complete a booking without help, using the playbook.
— ◈ —
CASE STUDY
Connecting a legacy insurance system to a modern
portal, without a rewrite
- The business problem
- A nationwide insurance firm had invested in a customer portal that could not talk to its
twenty-year-old desktop system. Staff re-keyed web submissions and downloaded, renamed and filed
documents by hand every day, and the backlog was eating into margins.
- Our leadership role
- We advised against the obvious full replacement, which would have meant years of re-creating
business rules in a regulated industry. We defined what data had to move, which rules governed it,
and where staff stay in control, then built a bridge that left the legacy system untouched.
- The result
- A multi-hour daily reconciliation became a guided review-and-approve workflow that takes minutes.
Transcription errors stopped, every transfer is logged, the portal became part of daily operations,
and staff kept the system they already knew.
Read the full case
study →
⟡ ⟡ ⟡
What is the process or project you want to move forward?
Tell us what is getting in the way, and we will help determine which scope fits.
Discuss your project