LinkedIn
LinkedIn
Hi, I’m Bartolomeo Tiralongo.
Fractional CTO

I build tech products
from zero to revenue.

Product strategy, architecture that holds, first hires. The technical lead of a CTO without the cost of hiring one.

↓ scroll
Get in touch

Where do we start?

Pick a channel, I reply within 48 hours.

01 · asynchronous

Send me an email.

[email protected] · reply in 48h
02 · synchronous

Book a call.

30 min · no pitch · Calendly
Philosophy

I come from a world where if the system fails,
something real stops. Not from slides.

I started at Ferrari, on powertrain controls, ISO 26262, functional safety. Then RINA, Industry 4.0. Then product, scale-ups, teams from scratch. Now I build products where the bug doesn't kill an engine but loses a customer, and to me, it's the same thing.

I don't sell hours of code. I sell decisions you won't pay for in five years: the right stack, an architecture that survives the next wave, a hire you won't regret, the "no" said at the right moment.

FIG. 01RITRATTO · B/N
[ drop · foto Bart al lavoro ]
luce naturale, B/N, non in giacca
Bartolomeo Tiralongo · aka Bart
Where I built
GaiaGo
’19–’21
Fiscozen
’21–’22
GoVolt
’22–’24
BRUM
’25–today
Plug and Play
mentor
GaiaGo
’19–’21
Fiscozen
’21–’22
GoVolt
’22–’24
BRUM
’25–today
Plug and Play
mentor

From understanding to shipping.

No templates. The pace adapts to where you are, whether you need a cold-eye reading, a hands-on lead, or a partner to scale.

/ 01
Week 1

Understand.

Two calls, no slides. I read the product, the team, the real constraints. You get back an honest map of technical risk.

  • 01Technical & organizational diagnosis
  • 02Hot spots and fast wins
  • 03Written report, not slides
/ 02
Week 2–3

Decide.

We commit to stack, roadmap and the 90-day yes/no in writing. Every decision has a reason and a stated cost.

  • 0190-day roadmap
  • 02Stack chosen with a reason
  • 03Decisions with a stated cost
/ 03
Month 1–3

Build.

Inside the team, 1.5 days a week. I unblock, review code, talk to vendors, hire who's needed.

  • 01Architecture put down
  • 02Steady delivery cadence
  • 03Critical hires done well
/ 04
Month 3+

Leave.

When the team walks on its own, I leave. What stays is a foundation that doesn't crack at the next fork.

  • 01Autonomous team
  • 02Living documentation
  • 03Continuity without dependency
Services

Three pillars. Five ways to work together.

01 · pillar

Decisions.

What to do, in what order, why, and what not to do.

Fractional CTO

Continuous technical lead for pre-seed and seed startups. 1.5 days a week, inside the team, written milestones every 30 days.

Tech Advisory

Sparring partner for founders. Bi-weekly calls, architecture review, presence in moments that matter.

02 · pillar

Architecture.

Systems that survive the next wave. And old ones that need straightening.

Technical Audit

Two weeks inside the code and the team. Output: written report, remediation roadmap, ranked risks.

Automation & AI in operations

Operational workflows cut and re-stitched with LLMs, integrations, pipelines. The boring work done by machines, reliably.

03 · pillar

Execution.

From the plan to the ship. The right people, at the right pace.

Product Management

Product roadmap, prioritization, user discovery, deciding what ships and what doesn't. Product in the hands of the people who build it.

Project Management

Delivery under control: milestones, weekly cadence, risk and dependency management. The plan that stays alive, not the one that rots in Notion.

Learn more →
Work

Things built, not slides presented. Specialty: zero → revenue.

/01

Tana della Tartaruga

Fractional CTO · 2024–present

Custom CRM · Telegram bot · automated email marketing.

Design and build of a custom CRM, integrated with a Telegram bot and an automated email pipeline. From Excel to structured data with automatic customer segmentation.

1
custom CRM
Telegram
bot integrated
auto
segmented emails
/02

BRUM Patenti

CTO · 2025–present

From concept to first MVP in store in 2 months. Today 150k downloads at 4.5★, 50k active/month.

Product roadmap, app live in 2 months, continuous iteration listening to real users. Web+mobile platform (quizzes, theory, document upload, payments, referral), integration with the Italian public driving portal.

150k
downloads
4.5★
store rating
2 mo
concept → MVP
BRUM Patenti: homepage della piattaforma live
BRUM Patenti · live platform · brumpatenti.it
→ app screenshots coming soon
/03

eWibe

Fractional CTO · 2024–present

Structural refactoring and stabilization of a live platform.

Alignment between product expectations, founders and technical debt. Performance, maintainability, stability. The hard part: saying no when needed.

⤴
stability
−40%
deploy time
✓
roadmap aligned
/04

GoVolt Mobility

Eng Manager · 2022–2024

Remote engineering team built from zero (6+), GCP cloud infrastructure, scalable microservices for logistics. From strategy to execution.

Microservice architecture for routing, battery swap, maintenance and analytics. 6+ engineers hired and managed remote. ETL pipelines and operational dashboards.

6+
engineers hired
GCP
microservices
0→1
team from zero
Learn more →
FAQ

The questions I always get.

01

How does it work concretely?

+

A day and a half a week inside the team, with written milestones every 30 days. Initial 3-month contract, monthly renewal after the first quarter. Flat monthly rate, no hours of code to account for. I'm in your Slack/Linear every day, not just billable hours.

02

What does Fractional CTO actually mean?

+

A part-time CTO, inside the team with a clear milestone-driven mandate. You pay for decisions and direction (architecture, hires, roadmap), not for hours of code.

03

How many startups do you work with at once?

+

Few, by choice. The quality of my work depends on not spreading thin. I'd rather say no than be a half-consultant.

04

Do you also write code?

+

Yes, when needed to unblock or to make architecture choices with my hands dirty. It's not the day job: the value is upstream (decisions, hires, architecture).

05

Do you also handle investors and due diligence?

+

Yes. Tech DD, calls with VCs, technical pitches. A big part of the job is telling tech well to people who don't build it.

06

How long does a typical engagement last?

+

Initial 3-month contract, then monthly renewal. Average engagement: 4–8 months. When I'm no longer needed, I leave: that's the success, not the failure.

I work with a few startups at a time. If there's room, I'll tell you right away.

Let's talk

Tell me what you're building.

An email, a voice note, a link to the product. In 48 hours I'll reply honestly: it's something I can help with, or not.

Send me an email
or book a call on Calendly
→ I’ll get back to you as soon as possible
Learn more →