“We already hired a team building our LegalTech platform — why do we need an architect too?” These two roles get confused often, and that’s understandable: both seem to be responsible for making the product work. In practice they solve different problems, and one doesn’t replace the other.
What a LegalTech platform developer does
A developer — or an integration studio — builds the system itself: the interface, the backend, integrations with external services, the database, the infrastructure. This is engineering work: turning a technical spec into a working, stable, scalable product. A good developer is responsible for code quality and for making sure the platform doesn’t buckle under load.
What a legal architect does
A legal architect doesn’t write code and doesn’t build the platform. My job is to determine, before a developer ever sits down at the keyboard: which decisions the product is allowed to make on its own, where the line falls between “the algorithm answers” and “the algorithm must stop,” which critical risks need to be built in as stop factors. I hand the developer finished logic — decision trees, a Red Flags matrix, specifications — not a technical spec written in a vacuum that they’ll have to figure out themselves, learning the law as they go.
Where the line falls: an example
The difference is clearest on a service that automates collecting small debts:
- The architect sets the logic in advance: under what conditions the service may send a demand letter and offer a payment plan on its own, and when it must stop and hand the case to a lawyer — for example, if the debtor disputes the amount, if the case falls outside simplified court-order proceedings (a debt over 500,000 ₽ under Article 121 of Russia’s Code of Civil Procedure requires a full lawsuit instead), or if there are signs the debtor is going through bankruptcy.
- The developer builds the system around that logic: the debtor’s account, integration with the register of enforcement proceedings, a payment gateway, notifications.
Without ready-made logic, the developer has to choose: either hard-code their own — legally risky — assumptions about when it’s safe to automatically press a debtor, or stop development at every edge case to check with lawyers as they go.
Why the architect isn’t an alternative to the developer
A legal architect doesn’t compete with the developer or the studio for budget — these are sequential, non-interchangeable stages. Without the architecture, the developer either invents legal rules themselves and takes on risks they’re not trained to assess, or the process stalls on every disputed case. Without the developer, the architecture stays on paper — a working product doesn’t assemble itself out of documents.
Sometimes this looks like an extra upfront stage — old-school waterfall instead of building in sprints. In practice it’s the opposite: without a ready Red Flags matrix and triage logic, an Agile team hits a wall on every edge case (“what do we do if the user has a mortgage?”) and stops the sprint to check with lawyers. Finished architecture removes these blockers in advance instead of delaying the build.
Some studios on the market offer “architecture” as part of a turnkey platform-build package. That’s a reasonable format for teams who want a finished product from one contractor, start to finish. But then the legal logic is designed by the same team that writes the code — without an independent check from a specialist for whom law is the primary specialization, not a secondary skill inside an engineering team.
The international market has reached a similar conclusion: OpenAI’s own partner network for rolling out AI at law firms hires former lawyers as “legal engineers,” not developers — the same principle of independent legal expertise, just at the scale of large international teams.
Frequently asked questions
We already hired a studio to build the platform — why do we need a separate architect? A studio can implement in code whatever logic it’s handed — the question isn’t skill, it’s independence of view. Even if the studio has a lawyer on staff, that lawyer’s job is to make sure the project ships on time and without complaints about the studio itself. An independent architect’s job is to protect the client’s business model, not the delivery deadline of a specific project. That’s a different lens, even at identical qualification levels.
Can the development studio itself design the legal logic as part of the project? Yes, some offer this as part of a turnkey package — and for some teams that’s a deliberately convenient format. The trade-off is that the same contractor both invents and implements the logic. In plain terms: it’s like hiring the same crew to design a house’s load-bearing walls and to sign off on their own work — the crew benefits from building however is easiest to pour concrete, not necessarily however keeps the house standing for fifty years. An independent architect isn’t there to get in the builders’ way — they’re there to make sure the house doesn’t come down.
Isn’t it too early to design a full legal architecture at the MVP stage? Partly, yes — if the cost of a mistake at MVP stage doesn’t exceed the cost of fixing it later. But in LegalTech and FinTech, a mistake at MVP stage can cost more than in average e-commerce: automatically sending out legally unfounded demand letters, or a personal-data leak with your first hundred users, is already a risk of a regulator complaint or a lawsuit — not just a bad review. You can scope MVP-stage architecture down to the key stop factors, but removing it entirely in a regulated market is risky.
Where do we start if the platform is already being built and there’s no legal logic yet? With the Core Architecture & Triage Logic format — I design the logic from scratch and hand it over in a form your current development team can pick up right away, without switching contractors.
Building a LegalTech or FinTech product and already have a development team in place? See how legal architecture works — the formats, and exactly what I hand off to the team. And if you’re not sure how this differs from a prompt engineer — that’s covered separately.