How I work
How I work — and when not to hire me
Hiring a freelance developer is scary, and the fear is legitimate. This page does not try to win you over with promises: it shows how I cut the risk, what lands in your hands from day one, and in which situations I tell you myself not to hire me.
The biggest doubt when hiring a freelance developer is not price or skill — it is trust: what if he disappears, what if I get locked into one person. I cut that risk with facts: your code and credentials are yours from day one, I use a standard stack any developer can take over, and we start small with scope agreed upfront.
Why hiring a freelancer stalls — even with a good proposal
I offered ready-made, working prototypes — for free — to several businesses, and I ran into the same wall every time. It was not the price (it was free) or the quality (it was live). It was risk: the feeling of handing something important to one person.
Behind almost every delayed decision lives the same silent question: "what if he disappears mid-project?" Add the fear of being locked to someone, of losing access to your own system, of having been burned before by an agency or freelancer. Those fears are fair.
What you can do is cut that risk at the root — through how I work, not through my promise that I am different. That wall is what gave birth to <a href="/projetos/vitriny/">Vitriny</a>, and it is what this page is about.
How I cut the risk
Your code and credentials
Source code, server, database, and accounts in your name from day one. You own the system, you are not a tenant — and on larger projects this is spelled out in writing.
Standard stack, no lock-in
PHP, MySQL, and JavaScript — technologies any market developer can pick up and continue. You are not locked into me or into an exotic framework.
Start small
We validate the highest-return piece before scaling. You see value early and decide the next step based on results, not promises.
Scope agreed upfront
Price and deliverables locked in before a single line of code. A new request mid-project becomes a new agreement with a price on the table — no surprise on the invoice.
People I have worked with
I will not ask you to take my word for it. These are people I have worked with who are willing to vouch for me — and, beyond my own projects, I provide IT services (as a contractor) to the team at <strong>Grupo Novo Tempo RH</strong>, in an ongoing engagement, not a one-off job that came and went.
"Working with Bruno means being certain of met deadlines and high quality. He has a very mature product vision, understands the needs of the business, and turns abstract requirements into robust solutions. An extremely reliable professional."
Rafael Souza
Global Talent Acquisition Manager · Tech & Executive Hiring
"Bruno is an exceptional developer. He not only delivers clean, well-structured code, but also has an incredible knack for solving complex architecture problems. He is the kind of professional who raises the technical bar of the whole team."
Janderson Sacilotte
Head de Marketing · Growth & Performance B2B
"Bruno's biggest differentiator is communication. On top of being a talented programmer, he can explain technical terms in a simple way and is always willing to help. It made all the difference in the success of our last project."
Thatiane Pierocini
Consultora em Liderança e Cultura · Gestora Comercial
When NOT to hire me
Trustworthiness also means saying no at the right moment. There are cases where I would be the wrong choice — and I would rather tell you now than after you have spent money:
- You need a large team by yesterday. I am a solo developer. At peak demand, with multiple fronts running in parallel, I deliver more slowly than a five-person agency — if that is the deadline, an agency will serve you better.
- The project is large-scale infrastructure. Very-high-volume systems with dedicated cloud architecture and an on-call team are not my strength. I would rather tell you that than accept the job and deliver poorly.
- You need 24/7 support. I do not cover round-the-clock on-call. I handle maintenance and support the delivery, but critical 24-hour operations require a structure that a single professional cannot sustain.
- Your process is not yet defined. If no one can explain how the current flow works, building software on top of it just cements the mess. First we organize it on paper — sometimes no system is even needed.
- There is an off-the-shelf tool that does the job. For standard needs — invoicing, payroll, accounting — buying ready-made or using a no-code tool is faster and cheaper. I will point you to the right tool and step aside.
Frequently asked questions
What if you disappear mid-project?
I deliver in increments, not in one big block at the end. Each piece goes live on your server and in your account, with documentation on how to manage it. If I vanished tomorrow, you would keep everything already running, in a codebase any developer can continue — because the code is yours and it is documented, not locked to me. On larger projects, this is formalized in the contract.
Will I end up dependent on one person?
That is exactly the right fear to have — and I work to make the answer no. I do not use exotic frameworks: PHP, MySQL, and JavaScript, which any market developer can pick up and continue. I deliver with a handover README. You are not locked to me; you own a system the entire market knows how to maintain.
Will the code and credentials really be mine?
Completely yours, from day one: source code, server, database, domain, and accounts in your name. You do not need my permission to continue with another developer or switch vendors. On larger services I formalize this in the contract, along with the scope.
I have been burned by an agency or freelancer before. How do I know this time is different?
Through two verifiable things, not my word. First, track record: more than 15 real applications published and free tools live right now (like PolicyForge and VulnGuard). Second, continuity with real people: I provide IT services, as a contractor, to the Grupo Novo Tempo RH team in an ongoing engagement — and there are people I have worked with who are willing to vouch for me (they are listed above). And in practice, incremental delivery means you never end up hostage to a single final handover.
You are a solo developer — is that not riskier than an agency?
The real risk of hiring one person is continuity, and I do not sweep that under the rug: what protects you is not my promise that I will not vanish — it is the code and credentials being yours and in a stack any developer can take over. In the worst case, you do not stop. In return, with a solo developer, you talk directly to the person building it, with no game of telephone and no overhead baked into the price. For deliveries that genuinely need a large parallel team, I will recommend an agency myself.
Custom-built software is expensive. Is it worth it, or should I buy off the shelf?
Off the shelf often works — and I will point you there when it does, instead of selling you a project. When custom-built makes sense, we do not bet everything at once: we start small, validate the highest-return piece with scope and budget agreed upfront before any code is written. If you want something extra mid-project, that becomes a new agreement — with a price settled before the work, never a surprise on the invoice.
How does it start?
With a free assessment call: you show me the problem and I tell you what is worth building, what is worth buying ready-made, and the expected return — including when the honest answer is "you do not need a system right now." If it makes sense to move forward, you receive a fixed quote (agreed upfront) before any work begins.
Want to talk through your risks before we start?
Tell me what is holding you back — the fear of being left stranded, losing control, or wasting money. The assessment is free and, within a short conversation, you will know whether it is worth building, whether something ready-made solves it, or whether the best move is not to build anything right now.
Or see what I can help with:Process automation · Custom-built systems · Digital presence & SEO · Security & LGPD compliance.