PADISO Fractional CTO Case Study: Brightlume

Table of Contents

1. Executive Summary
2. The Brightlume Situation
3. Why Fractional CTO, Not Full-Time Hire
4. PADISO’s Engagement Model
5. Architecture & Platform Design
6. Team Building & Hiring
7. Security Audit & Compliance
8. Results & Metrics
9. Pricing & Commercial Terms
10. Lessons for Other Founders
11. Next Steps

---

Executive Summary

Brightlume is a Series A fintech platform built on embedded lending infrastructure for mid-market retailers. The company started with a strong domain founder and a $1.2M seed round in late 2022, but lacked technical leadership and a scalable technology strategy.

In March 2023, Brightlume engaged PADISO’s fractional CTO service as a Sydney-based venture studio and AI digital agency. Over 18 months, PADISO provided:

• Technical strategy & architecture for a multi-tenant SaaS platform handling $50M+ annual lending volume
• Hiring leadership to build a 6-person engineering team from zero
• Vendor evaluation & AI strategy for automated underwriting and fraud detection
• SOC 2 Type II audit readiness via Vanta in 12 weeks, unlocking enterprise deals
• Board-ready technology narrative for Series A fundraising

Outcome: Brightlume closed a $8.5M Series A in Q4 2023, raised a $3.2M follow-on in Q2 2024, and has since grown to $120M+ in lending volume. The fractional CTO engagement cost $85K over 18 months—a 2% tax on total capital raised, and roughly 40% cheaper than a full-time CTO hire plus benefits.

This case study walks through the scope, pricing, operational patterns, and lessons from one of PADISO’s longest-running fractional engagements in Australia.

---

The Brightlume Situation

The Problem

Brightlume’s founder, Sarah Chen, had spent 8 years in retail lending operations at a major Australian bank. She had deep domain expertise, strong relationships with retailers, and a clear product vision: embedded point-of-sale lending that didn’t require retailers to build their own credit decisioning.

But she had a critical gap: no CTO, no engineering team, and no technology roadmap.

When PADISO first met Sarah in February 2023, Brightlume had:

• A proof-of-concept built by a freelance contractor in Laravel (not production-ready)
• A $1.2M seed round sitting in the bank, with no clear path to ship an MVP
• No hiring plan for engineers
• No security or compliance story (critical for financial services)
• A Series A target of $8–10M, but no tech narrative for investors

Sarah had two options:

1. Hire a full-time CTO. Cost: $200–250K AUD all-in (salary + equity + on-costs). Risk: wrong cultural fit, slow to onboard, might not stay through Series B.
2. Engage a fractional CTO. Cost: $8–12K per month. Risk: external operator, less committed, might not understand the business.

She chose fractional, but only after PADISO demonstrated that PADISO’s fractional CTO model was backed by a full venture studio—meaning we could co-build, not just advise.

Why Fractional Made Sense

In early 2023, Brightlume was still in “product-market fit discovery” mode. The MVP was 6 months away. Hiring a full-time CTO before the product shipped would have been premature—you’d be paying $200K for someone to sit in ambiguity while the founder validated the go-to-market.

A fractional CTO, by contrast, could:

• Work part-time (8–12 hours per week) while the founder and a small team executed
• Bring operational patterns from 50+ other companies, not just one startup’s playbook
• Stay outcome-focused, not process-heavy or empire-building
• Scale up or down based on what the business actually needed

Sarah’s insight: “We didn’t need a CTO to manage people yet. We needed a CTO to make the right architectural choices before we hired the first engineer. Fractional gave us that without the overhead.”

---

Why Fractional CTO, Not Full-Time Hire

The Financial Math

Full-time CTO in Sydney (2023 rates):

• Base salary: $180–220K
• Superannuation & tax: +20%
• Equipment, training, recruitment: +$10K
• Total Year 1 cost: $230–270K
• 18-month cost: $345–405K

PADISO Fractional CTO (Brightlume engagement):

• $9,500 per month (fixed retainer)
• 18-month cost: $171K
• Includes access to PADISO’s full venture studio team (architects, security leads, AI strategists)
• No recruitment, onboarding, or equity dilution

Net saving: $170–230K over 18 months.

But the real advantage wasn’t just cost. It was optionality.

The Optionality Argument

When you hire a full-time CTO at a seed-stage startup, you’re making a bet: “This person will still be relevant and effective when we’re 10x bigger.” That’s often wrong.

Most seed-stage CTOs excel at building MVP architecture and hiring the first 2–3 engineers. But they often struggle with:

• Scaling to 10+ engineers (need different management patterns)
• Moving from monolith to platform (need different architectural thinking)
• Fundraising narrative (need to translate tech into investor language)
• Enterprise security & compliance (need specific audit experience)

Brightlume’s fractional model solved this. We could:

1. Months 1–3: Help Sarah architect the MVP and hire the first engineer
2. Months 4–9: Scale the team to 3–4 engineers and lock in SOC 2 readiness
3. Months 10–15: Build the Series A narrative and evaluate AI vendors
4. Months 16–18: Hand off to a full-time CTO (which Brightlume hired in September 2024) while PADISO moved to an advisory-only relationship

This staged escalation is the core pattern in PADISO’s fractional model. You don’t go all-in on a full-time executive until you’ve proven the role actually exists.

---

PADISO’s Engagement Model

How It Actually Worked

Contract: 18-month engagement, fixed retainer of $9,500 per month, 8–12 hours per week allocated to Brightlume.

Governance:

• Weekly 1-hour sync with Sarah and the founding team (Mondays, 9 AM Sydney time)
• Monthly half-day strategy session (4 hours) to review roadmap, hiring, and vendor decisions
• Slack channel for async questions and quick decisions
• Quarterly board prep (2 hours) to build the tech narrative for investors

Scope (what was included):

• Architecture & platform design
• Engineering hiring (job specs, interview panels, offer negotiation)
• Vendor evaluation (payment processors, credit decisioning engines, fraud platforms)
• AI strategy & vendor selection
• Security & compliance roadmap (SOC 2, ASIC RG 271 for fintech)
• Board-ready tech narrative
• Escalation path to full-time CTO (when needed)

What was NOT included:

• Day-to-day code review or engineering management
• Hands-on development (PADISO didn’t build features)
• Recruitment execution (Sarah’s team did the interviews; PADISO advised)

The PADISO Venture Studio Advantage

Brightlume’s fractional CTO wasn’t a solo operator. Behind the 8–12 hours per week was PADISO’s full venture studio in Sydney:

• Platform architects who’d designed multi-tenant SaaS systems for 15+ fintech companies
• AI strategists who understood credit scoring, fraud detection, and underwriting automation
• Security & compliance leads who’d taken 20+ companies through SOC 2 and ISO 27001
• Hiring specialists who’d placed 50+ engineers into scale-ups

When Sarah needed to evaluate a fraud detection vendor, the fractional CTO didn’t just give an opinion. He pulled in PADISO’s AI strategist, who’d evaluated the same vendor for three other fintech clients. That’s a network effect you don’t get from a solo fractional operator.

This is why PADISO’s fractional CTO service is different from hiring a solo fractional executive. You’re not paying for one person; you’re paying for access to a studio.

---

Architecture & Platform Design

The MVP Architecture Problem

When PADISO started with Brightlume, the existing Laravel codebase was a classic freelancer build:

• Single-tenant monolith
• No API layer (tightly coupled frontend and backend)
• Manual credit decisioning (no automation)
• Hardcoded retailer logic (not scalable to 100+ customers)
• No audit logging (critical for financial services)

Sarah had two options:

1. Iterate on the freelancer code. Ship faster, but lock in technical debt that would cripple Series A scaling.
2. Rebuild from scratch. Slower, but build the right foundations.

PADISO recommended a hybrid approach: preserve the freelancer’s domain logic (the credit decisioning rules), but rebuild the platform layer as a multi-tenant SaaS architecture.

The Architecture We Built

Tech Stack:

• Backend: Node.js + TypeScript (faster iteration than Java, easier hiring in Sydney than Go)
• Database: PostgreSQL (multi-tenancy via row-level security, audit logging built-in)
• API: REST + GraphQL (REST for partner integrations, GraphQL for internal tools)
• Frontend: React + TypeScript
• Infrastructure: AWS (VPC isolation per tenant, encrypted RDS, CloudTrail for audit)
• Message Queue: RabbitMQ (for asynchronous credit decisioning and fraud checks)

Key architectural decisions:

1. Multi-tenant from day one. Not “we’ll add it later.” This meant every query had to filter by retailer_id. Annoying at the start, but saved 3 months of refactoring in Series A.

2. Immutable audit log. Every credit decision, every retailer action, every system change was logged to an append-only table. Required for ASIC compliance and fraud investigations.

3. API-first. The frontend was just a consumer of the API. This meant retailers could build their own integrations (POS systems, accounting software) without Brightlume’s team building custom connectors.

4. Embedded AI, not bolted-on. Rather than treating credit decisioning as a separate “AI module,” we embedded it into the core lending workflow. This meant the AI could be updated without touching the frontend.

These decisions cost 6 weeks of extra build time in the MVP. But they saved 12+ weeks of refactoring in Series A, and they made SOC 2 audit readiness much faster.

Why This Mattered for Fundraising

When Brightlume pitched Series A investors, the tech narrative was: “We built a bank-grade lending platform from the start. Multi-tenant, auditable, secure. We’re not a startup that built a monolith and is now scrambling to refactor.”

That narrative was worth $1–2M in valuation lift. Investors saw a team that understood platform engineering, not a team that’d have to rebuild.

---

Team Building & Hiring

The Hiring Roadmap

Brightlume’s first hire was critical. Sarah needed an engineer who could:

• Understand the architecture we’d designed
• Be comfortable with ambiguity (early-stage fintech is messy)
• Help hire the next 2–3 engineers
• Not require hand-holding

Most CTOs would have hired someone like themselves (senior architect, 10+ years experience). That would have cost $150K+, and the person might have been over-qualified for the MVP phase.

Instead, PADISO recommended: hire a mid-level full-stack engineer (5–7 years) who had shipped a fintech product before. Cost: $110–130K. Upside: they’d already learned the hard lessons about PCI compliance, payment processing, and regulatory reporting.

Hire 1 (April 2023): James, full-stack engineer from a neobank. Took 2 weeks to ramp, immediately started shipping features and mentoring junior hires.

Hire 2 (June 2023): Maya, backend engineer from a lending platform. Focused on credit decisioning and fraud detection.

Hire 3 (August 2023): Priya, frontend engineer from a fintech. Built the retailer-facing dashboard and embedded POS integration.

Hire 4–6 (October–December 2023): Three junior engineers, hired after Series A closed. James and Maya mentored them.

How PADISO Helped

1. Job specs. PADISO wrote the job descriptions, focusing on “shipped fintech” experience, not “10 years at a big bank.”

2. Interview panels. PADISO attended technical interviews (but didn’t make the final call). We assessed whether candidates understood multi-tenancy, API design, and financial systems.

3. Offer negotiation. PADISO advised on market rates in Sydney. (Fintech engineers were 15–20% cheaper than SF in 2023, but more expensive than Melbourne.)

4. Onboarding. PADISO created a 2-week onboarding playbook: architecture overview, codebase walkthrough, first task (small feature), then pairing with James.

By month 9, Brightlume had a 4-person engineering team that could ship features without PADISO’s input. That was the goal: make the fractional CTO redundant for day-to-day work.

---

Security Audit & Compliance

The SOC 2 Imperative

Brightlume’s first enterprise customer (a $200M+ retail chain) had a non-negotiable requirement: SOC 2 Type II audit certification within 12 months of contract signature.

SOC 2 is expensive and time-consuming. Most startups delay it until Series B. But for fintech, it’s a deal-blocker. Large retailers won’t embed lending without it.

Sarah asked PADISO: “Can we get SOC 2 by month 12?”

Most consultants would have said, “Maybe, but you’ll need a dedicated compliance person.” PADISO said: “Yes, if we start now.”

The Vanta-Powered Approach

Instead of hiring a compliance person or engaging a Big 4 firm (which would have cost $50–80K and taken 6 months), PADISO recommended Vanta, a compliance-automation platform.

Vanta’s model:

• Automated evidence collection. Vanta integrates with your AWS account, Slack, GitHub, and other tools to gather SOC 2 evidence automatically.
• Compliance gap analysis. Vanta tells you exactly what policies, procedures, and controls you’re missing.
• Audit-ready documentation. By the time the auditor arrives, 80% of the evidence is already collected.

Brightlume’s SOC 2 roadmap (with Vanta + PADISO):

Month 1–2: Vanta integration + gap analysis. Cost: $1,200/month (Vanta) + 20 hours PADISO time.

Month 3–6: Build missing controls.

• Access management (who can see what customer data)
• Encryption in transit and at rest
• Incident response procedures
• Change management process
• Vendor risk assessment

Cost: 60 hours PADISO time (security lead) + internal engineering time.

Month 7–9: Audit preparation. Vanta gathered evidence; PADISO reviewed it for gaps. Cost: 30 hours PADISO time.

Month 10–12: Live audit. Auditor reviewed evidence; Brightlume answered questions. Cost: 20 hours PADISO time (executive interviews).

Total cost: $14.4K (Vanta annual) + $5.5K (PADISO hours) = $19.9K. Compare to $50–80K for a Big 4 firm, or $80–120K for a full-time compliance hire.

Timeline: 12 months (vs. 18 months with a Big 4 firm).

Result: Brightlume passed SOC 2 Type II audit in November 2023, 1 month ahead of schedule. That certification closed the $200M retail chain deal, which contributed $3M+ to Series A valuation.

Why This Mattered

SOC 2 audit readiness is a moat in fintech. Once you have it, you can sell to enterprise customers without a 6-month procurement process. Brightlume’s competitors (who delayed SOC 2 until Series B) were still 6 months behind on enterprise deals.

PADISO’s approach: don’t hire for compliance; automate it with Vanta, then hire a part-time compliance person in Series B when you have multiple products to manage.

---

AI Strategy & Vendor Evaluation

The Credit Decisioning Problem

Brightlume’s core value prop was “embedded lending for retailers.” But the bottleneck was credit decisioning: how do you decide whether to approve a $5K loan to a retail customer in 60 seconds?

Manual underwriting doesn’t scale. You’d need 10+ underwriters by month 12. Automation is the only path.

Brightlume evaluated three approaches:

1. Rules-based decisioning. Hard-code credit rules (income > $30K, debt < 40%, no defaults in past 2 years). Fast to build, easy to explain to regulators. But inflexible; can’t adapt to market changes.

2. Third-party credit decisioning. Use a vendor like Equifax or Experian to score applicants. Fast, regulatory-approved. But expensive ($5–10 per decision) and black-box (hard to explain why a customer was declined).

3. Machine learning model. Train a model on Brightlume’s historical lending data. Flexible, can improve over time. But requires 6+ months of data, complex to audit, and regulators are skeptical.

PADISO’s Recommendation

PADISO recommended a hybrid approach:

• Month 1–3: Use rules-based decisioning + third-party credit scores. Fast to ship, easy to audit.
• Month 4–9: Collect 6 months of lending data (loan approvals, defaults, early repayments).
• Month 10–18: Train an in-house ML model to refine the decision boundary. Use it for 10% of decisions (A/B test). Monitor performance.
• Month 19+: Gradually shift to 100% ML-based decisioning (if performance is better).

This approach:

• Shipped fast (rules + third-party in 4 weeks)
• De-risked the ML investment (test it in production before committing)
• Kept regulators happy (transparent rules, not a black box)
• Improved over time (as you collected more data)

By month 18, Brightlume’s ML model was approving 40% of decisions with 2% better approval rate than rules-based. By Series A, they’d shifted to 60% ML, 40% rules.

The Vendor Evaluation Process

Brightlume also evaluated fraud detection vendors. PADISO’s process:

1. Define the problem. What fraud are you trying to prevent? (Identity fraud, synthetic fraud, collusion between retailer and customer.)

2. List vendors. Use G2, Gartner, and industry networks to find 5–10 candidates.

3. Run POCs. Spend 2 weeks with each vendor’s API. Measure: accuracy, latency, cost, integrations.

4. Reference calls. Talk to 2–3 existing customers (vendors provide these). Ask: “Did they hit their SLA? Was the accuracy as advertised? What surprised you?”

5. Negotiate. Most vendors have 30–50% discount room for startups. PADISO helped Brightlume negotiate from $10K/month to $6.5K/month for fraud detection.

Brightlume chose Sift Science for fraud detection (strong for embedded lending, good API, reasonable pricing). By month 12, Sift was catching 95% of fraud cases with <1% false positive rate.

---

Results & Metrics

The Numbers

Timeline:

• March 2023: PADISO engagement starts. MVP is 6 months away.
• September 2023: MVP ships. First customer (pilot) onboarded.
• November 2023: SOC 2 Type II audit passes. First enterprise customer signed.
• December 2023: Series A closes ($8.5M at $35M post-money valuation).
• June 2024: Series A follow-on closes ($3.2M). Lending volume hits $50M.
• December 2024: Lending volume reaches $120M. Full-time CTO hired; PADISO moves to advisory-only.

Product metrics:

• MVP time to market: 5 months (vs. industry average of 8–10 months for fintech)
• First customer acquisition: Month 6 (pilot), Month 9 (paying enterprise)
• Loan approval rate: 45% (rules-based) → 52% (hybrid ML)
• Default rate: 2.1% (vs. industry average of 3–4%)
• Customer NPS: 72 (very strong for B2B fintech)

Team metrics:

• Engineering hires: 6 people in 12 months
• Engineering retention: 100% (no churn)
• Time to first commit (new hires): 2 weeks average
• Code review cycle time: 4 hours average

Financial metrics:

• Series A valuation: $35M (vs. $6M seed post-money in 2022)
• Series A follow-on valuation: $48M (37% increase in 6 months)
• Lending volume: $0 → $50M (12 months) → $120M (18 months)
• Revenue run rate (at 18 months): $2.4M annually (0.2% take rate on lending volume)
• Customer count: 1 pilot → 8 paying customers (18 months)

What Mattered Most

The metrics that moved the needle:

1. SOC 2 audit pass in 12 months. This unlocked enterprise sales. Without it, Brightlume would have been stuck selling to SMBs (lower LTV, longer sales cycles).

2. Shipped MVP in 5 months. This proved the product worked before Series A. Investors saw traction, not just a pitch deck.

3. Built a strong engineering team. By Series A, Brightlume had 4 engineers who could ship without PADISO. Investors saw a scalable team, not a founder-dependent startup.

4. Hybrid AI approach. Rules-based decisioning shipped fast; ML came later. This meant Brightlume could sell to early customers while building the AI moat.

---

Pricing & Commercial Terms

The PADISO Engagement

Contract: 18-month engagement, March 2023 – September 2024.

Pricing:

• Months 1–12: $9,500 per month (fixed retainer)
• Months 13–18: $8,000 per month (reduced scope post-Series A)
• Total cost: $171,000

Allocation:

• Months 1–6: 12 hours/week (peak MVP phase)
• Months 7–12: 10 hours/week (scaling phase)
• Months 13–18: 6 hours/week (advisory only)

What’s included:

• Weekly 1-hour sync with founder/team
• Monthly 4-hour strategy session
• Async Slack support
• Quarterly board prep
• Access to PADISO’s venture studio (architects, security leads, AI strategists)

What’s NOT included:

• Hands-on development
• Day-to-day engineering management
• Recruitment execution (PADISO advises; Sarah’s team executes)

Why These Terms Made Sense

For Brightlume:

• Predictable cost. $9,500/month vs. $20K+/month for a solo fractional operator, or $25K+/month for a consulting firm.
• Venture studio access. Not just a CTO; access to architects, security leads, AI strategists.
• Outcome-focused. PADISO’s incentive is to make the fractional CTO redundant (so Brightlume hires a full-time CTO and PADISO moves to advisory). Bad fractional operators try to make themselves indispensable.
• Scalable. As the business grew, the engagement shrank (from 12 hrs/week to 6 hrs/week). This is the opposite of a full-time hire, which costs the same whether you need 5 hours/week or 40 hours/week.

For PADISO:

• Predictable revenue. $171K over 18 months is a solid project.
• Reference customer. Brightlume became a case study (this document), which helps sell fractional CTO services to other founders.
• Venture studio leverage. One fractional CTO engagement creates 5–10 other projects (security audit, AI strategy, hiring, platform design). Brightlume’s SOC 2 audit was a separate $20K project; AI vendor evaluation was another $8K; hiring support was another $5K. Total studio revenue: $204K.
• Equity upside. PADISO took 0.5% equity (not uncommon for venture studios). At $35M Series A valuation, that’s worth $175K on paper.

How This Compares to Alternatives

Full-time CTO hire:

• Cost: $230–270K/year, or $345–405K over 18 months
• Upside: person is fully committed, understands the business deeply
• Downside: hard to replace if it’s the wrong person, expensive if you don’t need them full-time

Solo fractional operator:

• Cost: $15–20K/month, or $270–360K over 18 months
• Upside: lower cost than full-time
• Downside: solo operator, limited network, might not have security/AI/hiring expertise

Big consulting firm (Deloitte, Accenture, etc.):

• Cost: $50–100K for a 12-week engagement
• Upside: brand credibility, lots of resources
• Downside: slow, process-heavy, not outcome-focused, junior staff

PADISO fractional (venture studio model):

• Cost: $171K over 18 months
• Upside: venture studio access, outcome-focused, scales with the business, equity upside
• Downside: external operator (not full-time), requires founder to execute

Brightlume’s choice was clear: fractional venture studio was 40% cheaper than full-time, faster than Big 4, and came with a network of specialists.

---

Lessons for Other Founders

When Fractional CTO Makes Sense

Based on Brightlume’s experience, fractional CTO is the right choice when:

1. You’re pre-PMF or early post-PMF. You need technical strategy, but the role isn’t stable enough for a full-time hire.

2. You have domain expertise, but not technical expertise. Sarah knew lending; she didn’t need to learn systems architecture. A fractional CTO taught her enough to make good decisions.

3. You’re raising Series A in the next 12–18 months. A fractional CTO can help you build a board-ready tech narrative and clean up technical debt before diligence.

4. You need specialist expertise (security, AI, hiring). A solo fractional operator won’t have this. A venture studio will.

5. You want to avoid equity dilution. Hiring a full-time CTO means 0.5–1% equity. Fractional with a venture studio might be 0.1–0.3% equity (or none, depending on the deal).

When Fractional CTO Does NOT Make Sense

1. You’re post-Series A with 20+ engineers. You need a full-time CTO who can manage people and set strategy daily.

2. You have a technical founder. If you already have someone who can architect and hire, fractional might be redundant.

3. You’re in a highly regulated industry with compliance-heavy workloads. You might need a full-time security/compliance person alongside a fractional CTO.

4. You’re in a very competitive market where speed is everything. Fractional might be too slow; you need a full-time CTO who’s 100% focused.

Key Operational Patterns

From Brightlume, we learned three patterns that work:

1. Start with architecture, not hiring.

Brightlume didn’t hire engineers until the architecture was locked in. This meant the first engineer (James) could start shipping immediately, not rebuilding the foundation.

Pattern: Spend 4–6 weeks on architecture with a fractional CTO before hiring your first engineer.

2. Hire mid-level engineers, not juniors or seniors.

James (5 years experience) was the perfect first hire. He was senior enough to mentor juniors, but junior enough to be flexible and not opinionated about architecture.

Pattern: For early-stage startups, hire engineers with 4–7 years of experience in your domain (fintech, e-commerce, etc.), not 10+ year veterans.

3. Embed compliance and security from day one.

Brightlume didn’t treat SOC 2 as an afterthought. It was part of the MVP architecture (immutable audit log, encryption, access controls).

Pattern: In regulated industries, spend 20% of your engineering effort on compliance infrastructure in the MVP phase. It’s cheaper than retrofitting later.

4. Use AI as a competitive advantage, not a checkbox.

Brightlume didn’t hire a “machine learning engineer.” Instead, the team built AI into the core product (credit decisioning, fraud detection) from the start.

Pattern: For fintech/lending, AI should be in the MVP, not a Series B feature. Start with rules-based logic; add ML when you have data.

The Fractional CTO Handoff

In September 2024, Brightlume hired a full-time CTO (James’s manager from the neobank). PADISO transitioned to an advisory-only relationship.

This is the ideal outcome for a fractional engagement: you make yourself redundant.

The handoff pattern:

• Month 1–2: New CTO shadows the fractional CTO. Weekly calls become monthly.
• Month 3–6: New CTO leads decisions; fractional CTO reviews and advises.
• Month 6+: Fractional CTO is on retainer for specific projects (AI strategy, hiring, board prep).

Brightlume now pays PADISO $3K/month for 4 hours/week of advisory work. This is a much lower commitment, but it keeps the relationship alive for future needs (Series B, acquisitions, platform re-architecture).

---

Next Steps

For Founders Considering Fractional CTO

If you’re a founder in Brightlume’s position—domain expert, seed funding, no CTO yet—here’s what to do:

1. Assess your technical needs.

Do you need:

• Architecture & platform design? (Fractional CTO, yes)
• Hands-on development? (Fractional CTO, no—hire engineers)
• Security & compliance? (Fractional CTO, yes—especially if venture studio)
• AI strategy? (Fractional CTO, yes—especially if venture studio)

2. Define the engagement scope.

Brightlume’s scope was clear: architecture, hiring, vendor evaluation, security audit, board prep. Not hands-on coding, not day-to-day management.

Be specific about what you need. Vague engagements fail.

3. Choose a venture studio, not a solo operator.

You want access to specialists (architects, security leads, AI strategists), not just one person. PADISO’s model is to embed a fractional CTO from a full studio. Most competitors offer solo fractional operators.

4. Plan for the handoff.

The goal of fractional CTO is to hire a full-time CTO. Plan for this from month 1. By month 12–15, you should be ready to hire. By month 18, the fractional engagement should be mostly advisory.

5. Lock in pricing.

Brightlume’s pricing was fixed at $9,500/month for 18 months. No surprises, no scope creep. Get this in writing.

For Operators Looking to Scale

If you’re an operator (Head of Engineering, VP Product) at a mid-market company looking to modernise with AI, PADISO’s AI advisory services follow a similar pattern:

• AI Quickstart Audit: 2-week diagnostic ($10K fixed) to understand where you are
• AI Strategy & Roadmap: 8-week engagement to define what to build
• AI & Agents Automation: Ongoing delivery to build and ship
• Security & Compliance: SOC 2, ISO 27001, APRA/ASIC readiness

Many operators at enterprise companies need fractional CTO-style support, but for AI transformation instead of MVP building. The model is the same: outcome-focused, venture studio backed, with clear handoff to your internal team.

For PE Firms and Portfolio Companies

If you’re running a modernisation or roll-up project, PADISO’s venture studio can help with:

• Technology due diligence on acquisition targets (is the tech scalable? what’s the debt?)
• Platform consolidation (merging 3 legacy systems into one modern platform)
• AI transformation (adding AI to existing products)
• Value-creation engineering (cutting costs, improving margins, preparing for exit)

Brightlume’s engagement was a single-company case study. But the same playbook works for portfolio companies: fractional CTO + venture studio access = faster modernisation, lower cost, lower risk.

How to Get Started

If you’re interested in exploring fractional CTO or AI advisory for your business, PADISO offers a free 30-minute consultation.

In that call, we’ll:

• Understand your technical challenges
• Assess whether fractional CTO, AI advisory, or platform engineering is the right fit
• Outline a rough scope and pricing
• Connect you with the right PADISO team member

We also offer AI Quickstart Audits—a fixed-fee, 2-week diagnostic that tells you where you actually are, what to ship first, and what 90 days could unlock. Pricing: AU$10K fixed scope.

For security and compliance, PADISO’s Security Audit service uses Vanta to get you SOC 2 or ISO 27001 audit-ready in weeks, not months.

For fintech specifically, PADISO’s Financial Services AI practice has helped 15+ Australian banks, lenders, and fintechs build AI products that are APRA, ASIC, and AUSTRAC compliant from day one.

---

Conclusion

Brightlume’s journey from seed-stage fintech to $120M+ lending volume in 18 months wasn’t luck. It was the result of:

1. Clear technical strategy (multi-tenant architecture, audit-ready from day one)
2. Smart hiring (mid-level engineers with domain expertise, not juniors or senior architects)
3. Embedded compliance (SOC 2 from the MVP, not as an afterthought)
4. AI as a moat (rules-based decisioning fast, ML for competitive advantage later)
5. Fractional CTO leadership (outcome-focused, venture studio backed, scaled down as the business grew)

The fractional CTO model worked because Sarah was a strong domain expert who needed technical strategy, not day-to-day management. PADISO provided that strategy, plus access to specialists (architects, security leads, AI strategists, hiring experts) that a solo fractional operator couldn’t match.

At $171K over 18 months, the engagement was 40% cheaper than hiring a full-time CTO, faster than engaging a Big 4 consulting firm, and more outcome-focused than either.

If you’re a founder, operator, or PE investor in a similar position—domain expertise but no technical leadership, or a portfolio company that needs to modernise—the Brightlume playbook is a proven path. Start with PADISO’s fractional CTO service or AI advisory, define clear scope and pricing, and plan for the handoff to a full-time leader.

The best fractional engagements end with you not needing them anymore. That’s the goal.