Reduce external dependency.
More operational needs should be solved inside Bridge rather than becoming another supplier brief or manual process.
01
Why this approach.
Nir's January goal is company-wide AI integration. The most effective route is not identical training. It is a set of complementary competencies designed around each person's role.
One curriculum is inefficient.
Different people have different roles, starting points and reasons to use AI. They do not need the same homework.
Build by competency.
Each person develops a focused AI capability that improves the work they are already responsible for.
Connect the capabilities.
Building, oversight, recurring automation and agentic research become one joined operating model.
The objective is not to make everyone equally technical. It is to make Bridge collectively more capable.
02
Build through levels, not generic AI training.
Each custom plan moves through the same four competency levels, but the practical skill at each level changes depending on the person's role.
Level 1
Foundation
Understand the tools, basic concepts, limits and safe working habits.
Level 2
Applied
Use AI reliably for real work with clear human review.
Level 3
Integrated
Connect AI into repeatable team workflows, tools and information systems.
Level 4
Autonomous
Use scheduled systems and agents to execute defined work with oversight and escalation.
03
Different people, different routes.
Together, the four routes create a more complete AI operating capability than teaching everyone to do the same thing.
Marc
August priority | Application builder
Vibe coding and internal tools
Marc becomes the person who can turn an internal need into a usable application. His starting point is rudimentary, so this begins with basic technical literacy and builds toward independent shipping.
- Understand files, formats and simple software architecture
- Scope a tool before building it
- Build, debug and improve applications with AI
- Deploy and share tools with the team
- Reach Lior's former practical capability, then move beyond it
Nir
CEO / Owner | Executive oversight
AI command and visibility
Nir does not need to be Bridge's strongest builder. He needs strong visibility, decision support and enough technical fluency to oversee how AI is being used across the company.
- Executive briefings and information compression
- Company and project oversight systems
- Decision-support workflows
- Structured visibility across team activity
- Akarii develops the practical operating layer while Peter supports technical governance
Tomer
Lower-touch route | Recurring skills
Scheduled cloud workflows
Tomer's route is deliberately lighter. The goal is to make AI work for him through recurring cloud-based tasks rather than asking him to spend large amounts of time operating AI directly.
- Scheduled briefs and recurring reports
- Automated information collection
- Repeatable cloud tasks
- Simple review and approval habits
- Low-maintenance AI embedded into normal work
Saul
Advanced route | Agentic research
Research agents and scoping
Saul's route is toward launching task-specific agents that can research properties, sectors and unfamiliar fields, then return structured findings for the business.
- Research-agent design
- Property and market scoping
- Cross-sector opportunity research
- Source validation
- Structured outputs with human review
PeterProduction-Grade Infrastructure
Peter provides the high-level CTO layer. He helps define architecture, security, reliability, deployment, recovery and the point at which specialist engineering is required. These technical standards and boundaries are aligned with Peter as the wider programme develops, with particular relevance to Nir's oversight role.
04
Why Marc comes first.
Marc has the clearest capability gap and the hardest practical route. August therefore focuses on getting this foundation right before the wider rollout.
What is vibe coding?
Using AI to help turn a business idea into working software without needing to manually write every line of code.
Marc describes what the tool should do, works with AI to build it, tests the result, fixes problems and then deploys or shares it with the team.
1Define the business need and structure.
2Use AI to build and iterate the application.
3Test, understand and safely share the result.
05
August commercial scope.
August is the committed work. It combines Marc's hands-on development with Peter's production infrastructure layer, using real Bridge needs wherever possible.
Peter
1 to 2
Production-Grade Infrastructure sessions
High-level technical guidance on moving from experiments to systems that can be trusted.
- Architecture and deployment standards
- Security, permissions and data handling
- Reliability and failure modes
- Rollback, recovery and continuity
- Technical governance for Nir
- Clear engineering boundaries
Freddy + Marc
8
Hands-on capability sessions
A practical progression from basic technical literacy to independently creating and sharing useful Bridge tools.
01
FoundationsFiles, formats, browser applications and basic software concepts.02
ScopingTurn a Bridge need into a clear product structure before building.03
Complete buildInterface, logic and data working together.04
Data and accessHosted backends, users and controlled access.05
DebuggingFind errors, recover from bad changes and avoid fragile patching.06
IntegrationsConnect services, APIs and recurring workflows.07
Independent sprintMarc leads a real Bridge build with support where needed.08
Ship and hand overDeploy, test, document and make the tool usable by others.Real Bridge build
At least one practical use case developed through the programme.
Reusable build method
A repeatable approach for scoping, prompting, debugging and iteration.
QA and deployment standard
A clear checklist for testing, access, reliability and safe release.
Documentation pattern
Enough structure for future ownership, maintenance and handover.
06
August to January.
The months after August are a proposed continuation roadmap, not a detailed commercial commitment. The focus is to introduce each route systematically and then connect them.
August
Build Marc and set the technical standard
Eight Marc sessions plus Peter's Production-Grade Infrastructure work.
Committed scope
September to October
Introduce custom routes
Begin Nir, Tomer and Saul's role-specific competency plans rather than repeating Marc's curriculum.
Proposed continuation
November to December
Connect the workflows
Bring oversight, internal tools, recurring cloud tasks and agentic research into shared operating processes.
Proposed continuation
January
Operate as one AI-integrated company
Different competencies work together as a single operating model.
Target state
January target
Marc can build. Nir can oversee. Tomer has recurring AI working for him. Saul can launch research agents. Peter keeps the infrastructure dependable. Together, those capabilities form one AI-integrated Bridge.