How we work

A mandate in writing.
An exit in the plan.

Every engagement starts with a written scope, runs on a fixed rhythm, produces documents you keep and ends with a handover.

Conversation · 30 minutes

You describe the situation.

Tell me what you have tried, what it costs and who uses it. I read the context before the call, and you leave it with one decision you can act on Monday. No pitch. If an engagement makes sense, a short written proposal follows.

You receive: a proposal with scope, deliverables and the first step.

Audit · 2 weeks

The map.

Every AI tool, subscription and experiment in the company, including what people use on their own, and what each one costs. A read on the data you already have. Short interviews with the people who use AI every day, and an hour with you.

You receive: a kill, fix or scale verdict on each one, three ranked bets and a cut list, a 90-day plan with a name next to each item, a memo you read in ten minutes and a 60-minute working session with your team.

Sprint · 90 days

From test to daily work.

The first 30 days are spent inside your business: how money comes in, where the work slows down, who does what. Then one or two bets go to work in the operation, each with an owner on your team and a number with a baseline. We meet for 45 minutes every week.

You receive: AI your team actually uses, with usage counted, a one-page AI policy, a runbook and the AI Bill at days 30, 60 and 90.

Retainer · 2 to 4 days a month

A Head of AI who stays.

A monthly review of the AI Bill, tool and vendor decisions, the next bet and adoption with your team. I direct the build with your team or with Tecela's builders.

You receive: the AI Bill every month, a log of every decision and the plan for the next bet.

Handover

The exit is planned on day one.

Runbooks, owners, policy and an internal successor are built as the work goes, not at the end. When the engagement closes, your team already runs it.

You receive: a handover pack. You can run everything without me.

Rhythm

A fixed rhythm.
Nothing else to manage.

This is the default rhythm. We adjust it to your calendar.

Weekly

Working session

A 45-minute working session with the owner of each bet. Blockers, decisions, next step.

Monthly

AI Bill review

One page for you: what you pay for AI and what came back, adoption and the decisions that need you.

Quarterly

Quarter in review

What worked, what was cut and the bets for the next quarter.

What you keep

Ten documents
you keep.

Everything is written, dated and yours.

  • Written mandateScope, decision rights, a spend ceiling you set and what still needs you. Above the ceiling, I recommend in writing and you decide.
  • Independence clauseAdvice and build in separate agreements, with a second option in writing for any Tecela build.
  • AI inventory and spend mapEvery AI tool, subscription and experiment, and what each one costs.
  • Kill, fix or scale scorecardEvery bet with its owner, its number and its verdict.
  • Decision logEach decision, who made it, why, and what it changed.
  • The AI BillMonthly: what you pay for AI and what came back, and adoption.
  • One-page AI policyWho may use which tools with which data.
  • Ten-minute memoThe Audit's findings and plan, written for you, not for engineers.
  • Handover packRunbooks, owners and the successor plan.
  • Source code and documentationFor anything Tecela builds, delivered to you.

On your clock

Your working day,
covered.

My hours sit one to two hours ahead of New York all year, so the gap with the US and Europe only moves when your clocks do.

My day starts one or two hours ahead of New York, so our working days line up almost completely. London and Central Europe overlap with my morning and your afternoon.

Your city My hours, in daylight time My hours, in standard time Your 14:00 is on my clock
New York, Boston, Miami1 hour ahead2 hours ahead15:00 or 16:00
Chicago, Dallas2 hours ahead3 hours ahead16:00 or 17:00
Denver, Salt Lake City3 hours ahead4 hours ahead17:00 or 18:00
San Francisco, Los Angeles4 hours ahead5 hours ahead18:00 or 19:00
London4 hours behind3 hours behind10:00 or 11:00
Paris, Berlin, Amsterdam5 hours behind4 hours behind09:00 or 10:00
 My hours stay fixed all year, with no daylight saving shift. US daylight time runs from March to early November and European summer time from late March to late October.

Security and data

Your data stays yours.
Access is tested.

Data is a sensitive asset. These rules go into the design from the first table.

Your data remains yours

Access is designed by user and organization, and tested at the boundaries.

Isolation by organization

In systems that serve several companies or clients, every table is separated at the data layer, row by row.

Numbers from code

Totals, dates and indicators come from explicit rules. A model never estimates a figure shown to a client.

Models by agreement

We decide with you what may go to an external model and what stays inside your own environment.

A log of every run

Inputs, tools used and results are recorded, so you can audit and improve.

NDA and DPA first

A non-disclosure agreement and a data processing agreement come before day one. Access runs only through accounts you scope.

Personal data is handled under our privacy policy.

Leaving

You can walk away
with everything.

The exit plan is part of the mandate from day one.

Runbooks, documentation, owners and an internal successor are built as the work goes. If you stop, nothing you need stays with me or with Tecela.

Next step

Let's define
the first step.

Tell me what is running today and who uses it. We start from that context.

Request a 30-minute call