About
Senior engineering, without the agency layer
WeInDev exists because there is a persistent gap between consultancies that produce strategy and vendors that produce code. Companies with real operational problems need someone who will do both, and stay accountable for the result.
Thirty years of building software teaches you which problems are technical and which only look technical. Most of the expensive failures are the second kind: a scope nobody agreed on, a decision made by whoever was available, a system that works but that nobody can safely change.
WeInDev was set up to work the way that experience suggests it should be done — paid discovery before commitments, senior people on the actual work, honest reporting when something is going wrong, and someone still accountable after launch.
Andre Camargo
Founder and Principal Architect
How we operate
What you can expect from us
Client outcomes over activity
Hours spent are an input, not an achievement. We report against the outcome the work was supposed to produce.
Simplicity over cleverness
The simplest architecture that safely supports your expected business. Complexity has to earn its place, every time.
Transparency over surprise
You hear about problems from us, early, while they are still cheap. Bad news does not improve with age.
Quality over shortcuts
Testing, deployment and documentation are part of finishing work, not a phase to be compressed when the date gets close.
Learning over defensiveness
We will be wrong about something on your project. What matters is how quickly we notice and say so.
Sustainable delivery over heroics
A team that needs weekends to hit a date will miss the next one too. We plan for the pace we can hold.
Fit
When we are the right partner — and when we are not
Being explicit about this saves everyone a month. We would rather refer you well than take work we are wrong for.
We are a good fit when
- The problem genuinely matters to the business
- Decision-makers will engage with the work
- The work sits in or near the Microsoft stack
- You want a partner who will disagree with you when it counts
We are the wrong fit when
- Selection is primarily on lowest hourly rate
- The scope is large but discovery is refused
- Certainty is expected that cannot reasonably exist
- The technology is well outside our competence and we have no strong partner for it
Technology
Deep in one stack, rather than shallow in twelve
Depth in a mature ecosystem produces more reliable systems than breadth across whatever is currently fashionable — and it means whoever reviews your architecture has seen this particular failure before.
- C# / .NET
- Blazor
- ASP.NET Core APIs
- Azure
- SQL Server / PostgreSQL
- CI/CD and infrastructure as code
- Applied AI