The things people ask
before they subscribe

Technical expertise, delivered as procedures you can execute. Each month you get credits. You spend them on technical actions written for your specific system, on verification of results you bring back, and on expert review by a person when a decision matters. Between those, the platform keeps a description of your system so every action gets more accurate rather than starting from nothing.

No, and the difference is the point. A prompt library gives everyone the same text. A technical action is generated for your stack, your infrastructure, your team and the decisions you already made, with a defined output format, evidence requirements and a verification step. You never see a numbered list of prompts, because that is not what you are buying.

No. TechnicalAngel helps you understand, audit, document and control software — including software you did not write yourself. If you need someone to implement the change, you still need a developer. What you get here is the plan they should follow and a way to check whether they did.

That is the main case it was built for. You describe the situation in ordinary words; the procedure is written in the language your AI tools and your developers understand. When a result comes back, you can ask for it to be read by an expert who will tell you in plain terms what it means for your business.

A credit is a bounded technical operation, not an hour. One credit is a personalised action or an independent verification pass. Two or three is a plan or a written expert review. Five is a full architecture or security audit. Eight is a recorded video review. You see the exact cost before you confirm anything.

They carry into the next billing cycle and are spent before the newer ones. Whatever is still unspent when the following cycle starts expires. So a quiet month is not lost, but credits do not accumulate forever.

Yes, in three pack sizes, from your workspace, without asking anyone. The balance updates as soon as the payment goes through.

The plan runs to the end of the cycle you have already paid for, and does not renew. Your project context, past actions and delivered reviews stay readable in your account so you can export what you need.

No, and by default you do not. The procedure runs inside your own environment with your own Claude Code or Codex, against your own repository. Only the result you choose to upload ever reaches us.

A description you control: stack, hosting, databases, integrations, team, vendors, constraints and previous technical decisions, plus whatever documents you upload. You can read and edit all of it, and you can see when it was changed.

No. Uploaded material is used to answer your question and to produce the review you asked for. It is not used to train anything and it is not shown to other customers.

Not without your explicit permission. A case can be marked as unusable for content, and nothing is published — anonymised or otherwise — unless you approve that specific text.

An experienced technical expert. The methodology is developed and maintained by senior engineers, and senior expert review is available when you ask for it. We do not claim that every generated procedure is personally hand-written from scratch each time — that would not be true, and it would not be a good use of anyone’s time.

A written review comes back within two working days. A video review within 24–48 hours of the material being complete. If something essential is missing you are told immediately rather than at the end of the window.

TechnicalAngel is asynchronous by design, and that is not a limitation we are apologising for — it is why a review that would need a scheduled meeting can instead be delivered overnight. Live sessions are an optional paid extra, not part of the plan, and they are never required to buy or to use anything.

The language on your account: English, Russian or Spanish. The expert may work in Russian; what reaches you is in your language, and for recorded review that translation is checked before delivery.