The Process
A Process You Can See, Not a Vibe You Have to Trust.
Why the Questions?
Enough Detail to Scope It Properly. Not a Technical Exam.
Each service uses a guided intake that asks enough to understand the goal, important boundaries, and obvious risks without expecting you to design the software for us.
Tell Us About Your Project
Create or sign in to your SBG account, complete the guided service-specific intake, and tell us what you are actually trying to accomplish. Submission starts review; it does not create a contract, charge you, or authorize work.
Scope & Review
SBG reviews fit and turns the request into a defined scope and proposal. This is where assumptions, exclusions, deliverables, schedule/start conditions, and price are made visible before anything is locked.
Approve & Sign
You review and respond to the current proposal first. If it is accepted, SBG presents the exact project legal package for a separate authenticated electronic signature. Proposal acceptance and legal signing are distinct actions.
Payment & Readiness
The applicable payment or approved authorization must be confirmed, and the practical start requirements for that stage must be ready — including the agreed scope, required documents, any required client materials, and any access SBG actually needs. Signing alone never starts production.
Work & Stage Reviews
SBG performs the authorized work and verification. Full Builds use two 50 / 50 stages: Stage 1 must be completed, presented, and explicitly accepted before the second 50% can become eligible. Atelier, Audit, and Rescue follow their approved one-stage structure.
Final Review & Handoff
SBG completes the final verification, documents known limitations, prepares any required source release, and records the handoff. For Build and Rescue projects, the Client Portal also provides project-specific Launch & Handoff guidance so ownership, deployment, accounts, ongoing third-party costs, first-use steps, and included support are understandable instead of ending at a ZIP file. Completed engagements then receive the applicable 30-day original-scope defect-reporting window; eligible SBG projects may later add annual Maintenance separately.
Explore Launch & HandoffWhat to Expect
Guided Questions, Plain-English Answers
A new Build starts without an existing product to inspect, so it naturally asks more about the people, main tasks, information, integrations, design direction, timing, budget, and anything that absolutely must not go wrong. Audit and Rescue can ask a shorter set because there is already an application to examine.
Plain English is preferred. Technical terms get short explanations where practical, “Not Sure” is a useful answer, and you do not need to arrive with an architecture diagram tucked under your arm. SBG translates the project goal into technical requirements during scoping.
We ask enough to expose assumptions before they become surprise work, surprise cost, or an awkward “I thought that was included” conversation. We do not ask you to paste passwords, MFA or recovery codes, secret API keys, private keys, or access tokens into the intake.
Annual Maintenance is a different lifecycle. It does not begin with a new-project intake; it attaches only to an eligible project SBG already completed and handed off. The applicable 30-day post-completion defect-reporting window remains separate from Maintenance. A timely qualifying case can continue after that reporting window closes; Maintenance is an optional additional annual service with its own bounded review/minor-corrective scope.
Scope & Change Management
Changes Are Classified, Not Nickel-and-Dimed
We don't run a rigid two-hour grace period, and we don't let “and also…” silently transform one product into another.
Minor Adjustment
Wording, small visual refinement, minor configuration. Handled without ceremony.
Scope-Neutral Change
Replacement of comparable behavior before implementation where practical.
Scope Expansion / Change Order
New workflow, role, integration, feature, redesign, or material architecture change. Handled openly.
After an approved scope exists, SBG may make reasonable technical, debugging, security, responsive-design, testing, and implementation decisions necessary to deliver — without requesting approval for every routine decision. That does not authorize scope expansion, third-party charges on your behalf, or destructive production actions.
Faster isn't always finished.
Debugging, testing, security review, permission review, integration testing, regression testing, and final verification all require time. Verification is never the schedule buffer.