Sprints per feature
The current cycle has allowed features to remain open across nine or more sprints.
Fractional CTO engagement
Clear answers in 30 days.
Hands-on leadership from day one.
A month-to-month engagement for SGL Financial that puts Steve Petersen inside the development team, creates a reliable delivery rhythm, and gives Gabriel a validated roadmap with practical choices.
Delivery cadenceRoadmap claritySecurityPerformanceAccountability
/01 · What we heard
SGL can ship. The missing layer is weekly technical leadership.
SGL's development team has shipped features before and can ship them again. What has been missing is someone embedded in the work every week: running the standups, getting the backlog ready, checking estimates, and telling Gabriel plainly where things stand.
Without that, features have taken nine or more sprints, QA cycles have stacked half-finished work on top of each other, and security and performance issues have been left open. Gabriel should be managing the business, not the CTO.
QA work stacking up
Half-finished work compounds when bugs and work in progress are not governed by clear rules.
Risks left open
Security and performance issues need a prioritized owner and a clear remediation sequence.
/02 · What SGL will know within 30 days
Four questions. Clear answers.
Select a question to see what Month 1 produces.
Output and quality
A grounded assessment of team delivery
An assessment of the development team's output, in both volume and quality, measured against what the team should be able to produce.
- Current output measured
- Quality reviewed
- Delivery gap explained
/03 · Operating model
Embed first. Improve delivery. Reduce cadence when the system is working.
The engagement changes shape as SGL gains control.
Embed and Audit
Steve joins delivery from day one, establishes the operating rhythm, validates the work, and completes the technical audit with support from Webisoft's AI-assisted audit and reporting tooling.
- Standups and sprint ceremonies
- Weekly backlog readiness with Gabriel
- Estimate validation and QA flow
- Delivery, security, performance, and scalability audit
- Month 1 Answers Report and 90-day plan
Hands-On CTO
Steve leads the chosen roadmap scenario toward predictable sprints, features shipped within 3 to 4 sprints, and risk-ordered security and performance remediation.
- Scenario delivery and ceremonies
- Backlog, quality, and estimate ownership
- Code and architecture oversight
- Risk-ordered audit remediation
- Accountability and handover planning for internal scrum master and product owner responsibilities
Strategic Oversight
Steve steps back from daily delivery and focuses on reviews, mentorship, architecture, AI adoption, and roadmap direction.
- Sprint reviews and monthly strategy
- Mentorship for internal leads
- Architecture and AI guidance
- Product roadmap direction
/04 · Scope and deliverables
Hands-on delivery leadership, backed by a technical audit.
Explore the workstream details.
Hands-on from day one
A repeatable weekly delivery rhythm
- Steve runs standups daily or three times per week.
- Sprint planning and sprint review follow the same fixed rhythm every week.
- Steve and Gabriel prepare top-priority features in a weekly backlog session.
- Each specification is AI-ready and scored for completeness before sprint entry.
- Developer estimates are reviewed before Gabriel plans against them.
- QA rules and work-in-progress limits stop half-finished features from piling up.
Roadmap scenario explorer
One audit. Three practical paths.
The Month 1 report will present each scenario with timeline, monthly cost, and risk. Choose a path below to explore the decision frame.
Steady pace
Keep the current team and improve the process only.
This path focuses on backlog readiness, validated estimates, QA flow, and a predictable sprint rhythm before capacity changes are considered.
TimelineDefined after audit
Monthly costDefined after audit
RiskExplained in report
/05 · Schedule and milestones
Visibility starts in Week 1.
Week 1
Embedded in delivery
Steve joins standups and sprint ceremonies.
Week 2
Early read
Gabriel receives an early view of team performance and pace.
End of Month 1
Answers and roadmap
The Answers Report, validated roadmap, prioritized findings, and roadmap scenarios are delivered.
30-day checkpoint
Choose the path
Gabriel and Webisoft select a scenario and set the Month 2 engagement tier.
Every FridayWritten status
What shipped, what is in progress, what is in QA, what is blocked, next sprint commitments, and open risks.
Every monthExecutive review
Sprint commitment hit rate, cycle time per feature, estimate accuracy, bug reopen rate, and open security items.
Response standardOne business day
Questions from Gabriel are answered within one business day.
/06 · Independence of the assessment
Advice delivered in SGL's interest.
Steve's assessment of the current team, pace, roadmap, and capacity will be based only on what the audit finds.
Improve before adding
The scenarios always include improving delivery with the current team before adding capacity.
Provider-neutral options
Options can include expanding the current team, hiring in-house, or using an outside partner.
Same criteria for Webisoft
If SGL considers Webisoft engineering services, they are evaluated on the same criteria as any other option.
No obligation
The Fractional CTO engagement does not depend on engaging Webisoft for engineering.
/07 · Investment
Choose the level of involvement SGL needs.
The tier is reviewed monthly against delivery targets and adjusted by mutual agreement before the next month begins.
Month 1
Embed and Audit
$9,000 USD · monthly fee
Hands-on delivery leadership from day one, the full technical audit, the Answers Report, and roadmap scenarios.
- Approximately 30 hours
- Open contract, month to month
- 30-day checkpoint included
Months 2 onward
Hands-On CTO
$9,000 USD · monthly fee
Daily involvement in delivery, backlog and estimate ownership, audit remediation, and weekly reporting.
- Approximately 25 to 30 hours per month
- Chosen roadmap scenario
- Monthly tier review
Once targets hold
Strategic Oversight
$4,500 USD · monthly fee
Sprint reviews, mentorship of internal leads, and monthly strategy sessions.
- Approximately 15 hours per month
- Reduced operating cadence
- Roadmap and architecture guidance
Hours are approximate and reflect the expected level of involvement, not a cap.
/08 · Conditions and terms
Clear operating conditions.
Access and participation
- SGL provides repositories, hosting environments, the project tracker, and existing documentation within the first week.
- The development team is available for standups and sprint ceremonies.
- Gabriel, or a delegate, is available for a weekly backlog session of about one hour.
Remote delivery
- Work is completed remotely from Webisoft offices or employee homes.
- Scheduled ceremonies are not missed. If Steve is unavailable, SGL receives advance notice and the session is rescheduled.
Security review boundary
- The review covers code and configuration.
- Penetration testing or a formal third-party assessment, if recommended, is quoted separately.
Commercial conditions
- Third-party costs such as hosting and APIs are covered by SGL.
- Out-of-scope requests are evaluated and quoted separately.
- Work begins once the initial payment is received.
- Payments are NET15. The initial payment is due on receipt.
Dependencies
- Webisoft is not responsible for outages caused by third-party services.
- Webisoft is not responsible for delays caused by the Client, including communication delays or new requests.
Invoice status
- Webisoft may pause work if more than one invoice remains unpaid, until outstanding payments are resolved.
Additional services, separate engagement
Engineering capacity is available if the roadmap calls for it.
Webisoft is a custom software and AI firm with about 40 engineers, based entirely in Canada and working in SGL's time zone with no language barrier.
Month 1 creates the decision point
Start with visibility. Choose the pace with evidence.
Steve embeds from week one. At the 30-day checkpoint, SGL chooses the roadmap scenario and the right level of ongoing CTO involvement.
Review next steps