Connector engineering · EBROTECH LLC
Your client's AI assistant cannot see inside the software they actually run on: Gesden, A3, Contasol, Presto, Holded, an ERP nobody remembers buying. We build that bridge, one program at a time, and keep it alive when the vendor changes something.
You keep the client, the brand and the retainer. We stay behind you, invoice you wholesale, and never appear in their panel.
What LegacyRail is
Every agency selling a CRM to local businesses hits the same wall. The pitch lands, the client nods, and then says: fine, but everything lives in Gesden. From there you either quote a project you cannot scope, or you walk.
LegacyRail is the part you do not want to quote. We open the program, pick a route in, move the records that matter, and stay on the hook for it monthly. Not a platform, not a marketplace, not 203 integrations in a catalogue. One bridge, per client, with a name on it.
The order of routes is fixed and we do not deviate from it: the official API first, then an export the client authorises, then reading their local database under a signed contract, and only last an agent driving their screen. We never touch the vendor's binary, and if all four are closed we tell you in the review and you keep the report.
# what a bridge looks like, on the inside
$ lr review --program gesden --version 2024.3.1
route: local SQL Server, read-only, DPA required
official API: none published
authorised export: partial (patients, no appointments)
$ lr build --to gohighlevel --dry-run
mapped 14 fields, 3 automations staged
dry-run ok · nothing written
$ lr verify --read-back
re-reading 412 records from the live account...
412/412 match what we sent
# a 2xx is not proof. We read it back before we call it done.
That is the shape of the work, not a public command line. There is no lr binary you can download today: the tooling ships with a build or a partner agreement.
Who this is for
LegacyRail sells to the person who builds or resells. The local business itself is served in Spanish under EBROTECH, by the same company, and that brand does not go near a client you introduced.
You already own the client and the relationship. You do not want to hire an integrations engineer for one deal, and you do not want to say no. Wholesale price, white-label delivery, we never contact your client directly.
You are deciding whether to build the connector yourself. Read what we did before you spend the fortnight: the slim two-tool MCP surface, why thirty tools per session is a token tax, and how the read-back gate works.
How it works
01
5 business days
We read the software ourselves: the official API if there is one, the export routes if there is not, the shape of the database, and what the licence actually permits. You get the report and the fixed quote whether or not you go ahead.
02
3-4 weeks
One bridge, one program, over the most honest route available. The data lands in their CRM and their assistant, and three automations run on their real records. The data processing agreement is signed before anything is touched.
03
Monthly, not optional
Vendors change fields without telling anyone. The monthly fee is what turns a demo into infrastructure: we watch it, we fix it when it breaks, and your client never finds out the hard way.
Between step one and step two there is a signature and a data processing agreement, always in that order. We do not read a client's database on a handshake, and we will not start a build without one.
The ladder
Europe pays in euros, everywhere else pays the same figure in dollars. No conversion games, no "contact us for pricing" on the rungs that have a price.
$497 · €497 one-time
In one week you get a straight answer: what an AI assistant can and cannot do with the software your client already runs, what is automatable on Monday without touching anything, and what the full bridge would cost.
Where the line is: No code is written and nothing is installed at this step.
$1,497 · €1,497 one-time
The same work across a real stack: three or more programs, two stakeholders, and three costed routes: do it in-house, have us do it, or hire a consultancy.
Where the line is: Still no code. This is the map, not the track.
Where the work actually is
$2,997 · €2,997 build $197 · €197 per month, required
One bridge, one program, built the most honest way that exists in that case. The client keeps the software they refuse to replace; their assistant finally knows what is inside it.
Where the line is: We never touch the vendor's binary, and we never ship a bridge without the monthly. A bridge nobody maintains is a bomb on a timer.
$9,997 · €9,997 project $497 · €497 per month
Two to four programs connected, the CRM built for the vertical, a voice agent, quoting and invoicing, history migrated, the team trained, and three months of us next to them.
Where the line is: One at a time. It consumes the only resource that does not scale.
$1,997 · €1,997 per month, 3-month commitment
Not a project. A monthly block of our time against your stack: you decide each month what gets built, and it gets built.
Where the line is: Two clients at a time. Selling a third would mean not delivering, so we do not sell a third.
What we have shipped, and what we have not
Everything below was counted on disk or run on a machine, not copied from an older document. If a number is not here, we do not have it.
We publish this because the first question any serious buyer asks is "show me one working", and the answer today is that we cannot. Everything else on this site is easier to believe once that is out of the way.
For agencies
Wholesale is $1,997 · €1,997 per bridge plus $97 · €97 a month. Partners resell it at 3,500-4,500 with 250-300 monthly, which is the market rate for the same work done badly by someone else.
Questions we get asked
Written, not proven. Twenty connectors exist in our codebase and every one of them was built against mocks: none has ever run against a real installation. What we do have is the path, the Windows agent packaged with its installer, the .bc3 reader for Presto, and the data processing agreement drafted. If you are the first on a given program, you are the first, the price says so, and you get 30 days to walk away.
Never the binary. We take the most honest route that exists in each case, in this order: the official API, an export the client authorises, reading their local database under a signed contract, and only last the agent driving the screen. If a vendor's terms forbid all four, we say so in the review and you keep the report.
Under this brand, our customer is you. LegacyRail sells to agencies, consultants and developers. The retail brand for local businesses is EBROTECH, in Spanish, and it does not go anywhere near a client you introduced. If that matters to you, put it in the partner agreement and we will sign it.
Because a bridge nobody maintains is a bomb on a timer. The day the vendor changes a field, the client blames whoever built it, and they blame them for free. The monthly covers the fix and the watching. No bridge ships without one.
The build fee comes back within 30 days. That is the whole guarantee and it is deliberately boring: we would rather refund one build than argue about whether a half-working bridge counts.
Two builds a month, one full rebuild at a time, two monthly retainers at a time. Those are hard limits and they are published because selling past them would mean not delivering.
No. You buy the result and the maintenance, not the machine. The MCP server, the CLI and the templates stay on our side, which is why the output stays current. If your client needs an escrow arrangement for continuity, ask and we will price it.
Tell us which software is blocking the deal and we will tell you, for free, whether there is a route in. If there is, you get a fixed quote. If there is not, you get a straight no in writing, which is worth something too.