Hiring and risk
Months of recruiting and six months of salary before you find out whether the CV was true.
Changing priorities
Every adjustment in the operation becomes a contract amendment or a new quote.
Code ownership
Tied to perpetual monthly licences or to code you don't control.
Who you deal with
A salesperson promises, a manager passes messages along and a junior learns on your project.
Success cases
Five Operations. Five Different Kinds of Chaos.
Real systems in operation, built, optimised and maintained by RysDev
Success case 01 RP BLOCK
An entire factory that wasn't written down anywhere.
They knew how much they had to produce — it wasn't written down anywhere. They knew production had to be logged — it wasn't written down anywhere. They knew the concrete block recipe — it wasn't quantified anywhere. There were scattered spreadsheets and a PHP system so old, so full of holes and so slow that nobody opened it at all.
The entire production chain of a 25,000 m² plant now lives inside one system, built from scratch. It started in Bubble, because what the factory needed was to start measuring fast; it is being rewritten in code now that the size of the problem has outgrown what the platform can carry. The two run in parallel — the old one still serves as reference until the new one can stand on its own legs. The company's most important asset, the block and the paving slab, finally has numbers, history and traceability.
Success case 02 Soffcal
A calculation that forgives no mistake, turned into a form.
Sizing a photovoltaic system is a long, sensitive calculation full of variables. Every installer did it their own way, with no defined method — and a mistake only surfaced after installation, when it was too late to undo.
Soffcal standardises the calculation for any kind of system — on-grid, off-grid, hybrid or BESS — and turns hours of arithmetic into minutes of form-filling. Any installer can run it, and repeat it without divergence.
Success case 03 GREIC
A stalled project that shipped in two months.
The IPEN/CTMSP staff club, on the University City campus, needed to manage bookings of recreational spaces for members and non-members, under a rulebook of exceptions no generic calendar can handle. The system had been built inside the club itself, badly, and the first attempt to redo it — run by a junior developer — never got off the ground.
RysDev joined the project and rebuilt almost the whole system in two months. Not just writing code: discovering the business rules alongside the client, in real time, in the same room. It is live, in use, with the full rulebook of exceptions inside it — and the club's roughly 3,000 members being registered.
Success case 04 Start G4
Five years as a company's entire IT department.
The CEO had the business, the clients and the ideas. He had no technology structure at all to turn an idea into a system, and building a team was not an option for someone still operating as a sole trader.
For four to five years it was just the two of them: him as business analyst, RysDev as the IT department. That pair produced seven to ten systems — one for every new idea that came along. It is this entire page summed up in a single client.
Success case 05 BuyTicket Brasil
Bubble's largest client in Brazil, too big for the platform.
BuyTicket picked a niche where it stood alone and grew too fast: R$ 1 million in revenue in its first year of existence. It became, according to Bubble itself, the platform's largest client in Brazil — and too big for its structure.
Two years of technical consulting, three meetings a week with the whole team. There was no single problem: there was every problem that came up in a critically available environment — cutting platform cost, optimising flows, business rules, automation with n8n, and the bridge between the people selling and the people building.











