Where it is fragile, where it will not scale, and which parts are load-bearing. Test coverage where it matters and where it is theatre.
Brunescco Consulting
Built, fixed,
or read honestly.
Brunescco makes its own applications. The same team takes on work for other people: a product carried from nothing to the store, one problem a team has been circling for months, or an independent audit of a system already carrying real traffic.
Three ways in
-
01
Build it
A product taken from an idea to something installable. Design, mobile, desktop, backend, and the words on every screen, handled by the team that will still be there when it ships.
-
02
Fix one hard part
The realtime feature that will not hold under load. The interface that stopped making sense as it grew. The build nobody wants to touch. Brought in for the part that is actually difficult, and out again when it is done.
-
03
Audit what exists
An outside read of a system already in production, delivered in writing. No access to your repositories is needed to start the conversation, and no engagement follows unless you want one.
Audits
A system read by somebody who did not build it.
Teams grow close to what they made. The compromise agreed under deadline two years ago becomes the way things are done, and nobody in the room can see it any more. An audit is an outsider reading the whole thing with fresh eyes and no stake in the decisions that led there.
Larger organisations use this before a rebuild, before an acquisition, after an incident, or when a compliance question needs an answer that is not written by the people being asked about.
What the product collects, where it goes, who else receives it, and how much of that is necessary. Written so a lawyer and an engineer can both read it.
Speed on a real device, contrast and keyboard access measured rather than assumed, and the places where the interface works against the person using it.
What is fragile, what it is costing, what to do first. It names the parts that are fine, because an audit that finds fault everywhere is not reading, it is selling.
Fixing what an audit finds is a separate conversation, and never a condition of it.
How it runs
- At a time
- A small number of projects, so each one gets the attention a Brunescco product would get
- Who you talk to
- The people doing the work, not an account manager relaying it
- Reporting
- Written, in plain language, at a rhythm you set
- Handover
- Documented well enough that your team can carry it without Brunescco
- Confidentiality
- NDAs signed before anything is shown, as a matter of course
- Scope
- Agreed in writing before the work starts, and revisited in writing if it changes
The same standard as everything else with this name.
The four rules the products answer to apply here too. Nothing is delivered half-finished and called done. Nothing collects data it does not need. Nothing is built to be hard to leave, including this arrangement.
Contact
Say what you are building, or what is going wrong.
geral@brunescco.comClick the address to copy it, or open it in your mail app. No form, no scheduling link, and replies come from the people who would do the work.