AC

How I work

Two decisions. Pick the one that is stuck.

I do not sell a menu of capabilities, and I do not sell sprints of general AI work. There are two decisions I take on, and both run through TechTide AI, where the scope and the pricing live.

This page is the router. It tells you which engagement is yours and hands you to the page that spells out how it runs.

The two decision engagements

Decision 01

Systems Decision Audit

An AI workflow blocked between a working demo and dependable operations.

Returns one decision: Ship, fix, redesign, or stop.

Signals

  • A pilot that has been two weeks from shipping for two quarters
  • Agents with no evals, no traces, and no blast-radius limits
  • Model spend nobody can attribute to a workflow
  • Nobody willing to say out loud whether it is safe to trust

Ninety minutes with the people who built it, then a written call: ship it narrow, fix a named list first, redesign the approach, or stop. The reasoning is on the page, so your team can argue with it.

Systems Decision Audit at TechTide AI
Decision 02

Airtable Rescue Decision Sprint

A business-critical Airtable system that now decides what operations can do.

Returns one decision: Stay, stabilize, hybrid, or exit.

Signals

  • Core operations living in bases nobody fully understands
  • Record, automation, and per-seat limits shaping process
  • No real access control on data that should be locked down
  • Reporting that needs a human to reconcile it every week

A sprint through the real domain model, the limits you are actually hitting, and the cost of each option. It ends with stay, stabilize, hybrid, or exit, plus what the first move costs you either way.

Airtable Rescue Decision Sprint at TechTide AI

The rest of the ladder

One step smaller, one step later.

Production Block CallSmaller way in. One named blocker, one call, one recommendation. Take it when you already know which blocker is costing you the most.Critical System ImplementationThe build step. Application only, after a decision engagement, fixed scope. It follows a decision engagement, never replaces one.

FAQ

Common questions.

Why only two engagements?
Because they are the two decisions I am genuinely the right person for. An AI workflow stuck between demo and dependable operations, and a business-critical Airtable system that needs a stay-or-go call. Anything else, I refer out.
Where does the pricing live?
On TechTide AI. This site is my personal record: how I think, what I have shipped, and what I have written. TechTide holds scope, sequencing, and price for every engagement.
What do I actually get?
A written decision. The Systems Decision Audit returns ship, fix, redesign, or stop. The Airtable Rescue Decision Sprint returns stay, stabilize, hybrid, or exit. Each one names the reasoning, the risks, and the sequence.
Can you just build it instead?
Critical System Implementation exists for that, and it is application only after a decision engagement, on fixed scope. I do not start with a build, because most stalled systems fail on a decision, not on code volume.
What if I have one specific blocker?
Take the Production Block Call. One named blocker, one call, one recommendation. It is the smallest way in and it credits toward a decision engagement if you go further.
Who do you work with?
Founders, CTOs, and operations leads. Mostly US, with Canada and EU teams on async overlap.

Still not sure which decision is yours?

Send me two sentences about what broke last week. If neither engagement fits, I will tell you that too. Technical proof lives on alexcinovoj.dev.

alex@techtideai.io