Strategic AI Advisor & Architect

01

Purpose

To own the AI infrastructure, tooling strategy, and technical architecture that the Surge Intelligence platform is built upon — ensuring the foundations are properly designed, implemented, and maintained so the operational team can execute with confidence.

Working title open to refinement based on our conversation

02

Domain Authority

The areas where this role holds the lead view and architectural ownership.

AI Tooling Selection & Configuration

Ruflo setup and orchestration, Claude API integration, AI video and production tools, and any future additions to the AI layer. Selection, configuration, and ongoing management.

Technical Infrastructure

Environment setup, Supabase architecture, Vercel and GitHub configuration, and API key management across Anthropic, PandaDoc, Microsoft Graph, and Xero.

Architecture Validation

Confirming the platform's build sequence, data model, tech stack decisions, and integration design are sound before execution begins. The sign-off layer before code is written.

Staging & Quality Environment

Designing and maintaining the staging environment that mirrors production — the foundation for all testing, UAT, and quality assurance before deployment.

03

Ongoing Contributions

Recurring strategic input beyond the initial build phase.

AI Tooling Strategy

Staying ahead of new tools and capabilities that can accelerate the build or enhance the platform's intelligence layer — bringing relevant opportunities to the team before they become obvious.

Architecture Review

Periodic validation that the platform's technical foundations remain sound as it scales through each build phase. A checkpoint that protects the integrity of what's been built.

Marketing AI Tooling

Finding and accessing the AI production tools — video, design, content generation — that give the team a competitive execution edge on the Surge Intelligence launch and ongoing campaigns.

04

Engagement Model

How this role is structured to deliver maximum output with full architectural focus.

Working Days

Mon – Thu

Four-day advisory engagement. Friday outside scope.

Engagement Type

Advisory Retainer

Scoped advisory arrangement — not embedded employment.

Meetings

Selective

Milestone checkpoints and key decision gates. Async updates for daily stand-ups.

Review Point

3 Months

Engagement reviewed at 3 months. Pathway to 3 days as platform matures.

Retainer terms and specific meeting cadence to be agreed

05

Team

1 Execution Resource (short term)

One direct execution resource to support delivery. No day-to-day people management responsibilities — architectural input and direction only. Management of the broader team remains with Nick.

06

What This Enables for Focus

The value this structure creates for the business and for the build.

I

Full command clarity for Nick Nick retains complete decision authority over the business, product direction, and team. The AI and infrastructure layer has its own dedicated owner — no gaps, no ambiguity.

II

A properly architected foundation from day one The platform is built on infrastructure that has been deliberately designed, not assembled on the fly. Every technical decision made before code is written, not after.

III

Protected, focused contribution Architecture and AI strategy work requires deep, uninterrupted focus. A bounded advisory engagement produces better output than fragmented operational presence.

IV

An intelligence edge that compounds Having a dedicated AI tooling strategist ensures Focus always has access to the most effective tools and approaches — not just at launch, but as the landscape evolves.