Architecture review · fixed price, one week
A one-week architecture review with a fixed-price next step
Before you rewrite it, hire for it or raise money on it, know what you have. A senior engineer reads your code, your infrastructure and your release process, and tells you in writing what to fix first, what can wait, and what the next step costs. $2,500, one week, yours to keep.
Architecture review (1 week): $2,500
A software architecture review is a short, fixed-price assessment of a codebase, its infrastructure and the way it is released. In one week you get a written report with risks ranked by impact, the quick wins, the cost of doing nothing, and a fixed-price proposal for the next step, yours to take anywhere.
When a review pays for itself
Typical situations (not client quotes)
- We inherited a codebase nobody on the team fully understands, and the person who wrote it is gone.
- Releases keep breaking production and every fix takes longer than the last.
- An investor asked for technical due diligence and we do not know what they will find.
- Two vendors quoted a rewrite. One said six months, the other eighteen.
Most expensive software decisions are made without an independent read of the system: rewrites that were not needed, hires for the wrong skill, cloud bills that nobody questions, security basics that nobody checked. A review is cheaper than any of those mistakes, and it gives you a document you can put in front of a board, a buyer or a new engineering lead.
We also use it as our own first step. If you are considering us for a bigger project, the review is how we avoid quoting blind.
What you get
A senior engineer with read-only access, under NDA, spends the week on four things: the code and its dependencies, the infrastructure and what it costs, the security basics, and the path from a commit to production. On day five you get a written report and a walkthrough call with your team.
We review the way we run our own systems. On the platform we operate, every Guiadalajara release backs up the database before anything changes, releases go out blue/green and the infrastructure is written as code; those are the standards we hold your system to, and we are explicit about which ones matter for you now and which ones do not. Cost is part of the review, not an afterthought.
- Code and dependency review: structure, tests, outdated or risky packages
- Infrastructure and cost review: what runs where, what it costs, what is oversized
- Security basics: secrets, access, backups, exposure
- Delivery process: from commit to production, and how a bad release gets rolled back
- Risks ranked by impact, each with an estimated effort to fix
- Fixed-price proposal for the next step
- Walkthrough call with your team, recorded if you want
What you get · Architecture review
Written report
Findings ranked by impact, quick wins, and the cost of doing nothing. Written for the people who decide, with the technical detail in an appendix.
Walkthrough call
One hour with your team: questions, context, what we would do first.
Fixed-price next step
A scoped proposal for the first fixes or the modernization plan, with a price in writing. Take it to us or to anyone.
Infrastructure map
What runs where, who has access, what it costs per month, what has no backup.
Proof · Architecture review
We hold your system to the standards we run ours on: backups before every release, blue/green deploys, infrastructure as code, and payments that are never left without their record.
- every Guiadalajara release backs up the database before anything changes — Source: Our own platform (Guiadalajara), in production, checked October 16, 2026
- no PayPal charge is ever left without its booking: the booking is saved before the charge and an automatic reconciliation closes the gaps — Source: Client case, published with permission, checked October 16, 2026
Own platform
Guiadalajara
Our own platform for local businesses in Guadalajara: marketplace and directory, appointment booking by business type, point of sale and CFDI e-invoicing, on web and mobile apps.
See the case →
Transportation
VIP Transportation
Luxury private transport in Puerto Vallarta, booked in 6 steps with not a single payment ever falling through the cracks.
See the case →
How we work · Architecture review
Access
Read-only access to the repository, the cloud console and the deployment pipeline, under NDA. A thirty-minute call with whoever knows the system best.
Day 1
Review
Code, dependencies, infrastructure, cost, security basics and release process. We write as we go.
Days 2–4
Report
Findings ranked by impact, with effort estimates and the fixed-price proposal for the next step.
Day 5
Walkthrough
One hour with your team. Your questions, our recommendation, and what we would not touch.
Day 5 or the next business day
Pricing · Architecture review
| Item | Price |
|---|---|
| Architecture review (1 week) | $2,500 |
| Legacy modernization, scoped after the review | from $25,000 |
Paid up front, in US dollars, by wire transfer. Or start with a free 30-minute intro call. Full rate card on the pricing page.
Questions · Architecture review
Do you need write access to our systems?
No. Read-only access to the repository, the cloud console and the pipeline is enough, and we return it at the end of the week. Everything is under NDA.
Do we have to hire you afterwards?
No. The report and the proposal are yours. Many clients use them to brief their own team or to compare vendors; if you do hire us, the $2,500 comes off the project price.
Which stacks do you review?
Mostly TypeScript and Node, Next.js, Python, PostgreSQL, Flutter and Swift, on AWS, Google Cloud, Linode or your own servers. If your stack is different, say so on the call and we will tell you honestly whether we are the right reviewer.
Is this technical due diligence for investors?
It can be. The report is written so a non-technical reader can follow the risks and the costs, with the technical detail in an appendix. Tell us who the audience is and we will structure it for them.
How fast can we start?
Usually within a week of the intro call, as soon as access is in place. The review itself takes five business days.
What does the next step usually look like?
Either a short list of fixes we can do in weeks, a monthly support plan to stabilize what you have, or a modernization plan by stages when a rewrite is actually warranted. The report says which, and why.
How do we pay, and who do we contract with?
Up front, in US dollars, by wire transfer. You contract with our Mexican company; its legal name and tax ID go on the invoice, and we provide a W-8BEN-E on request.
Know what you have before you rewrite it
One week, $2,500, a written report you can put in front of anyone.