Fixed fee · 10 working days · Led personally by the founder
Bring one decision that is holding up a customer promise, roadmap, rewrite, or major technology spend.
The product is getting harder to change, delivery keeps slowing down, and nobody agrees whether targeted repairs or a rewrite will solve it.
A major customer or product commitment is on the table, but the team is not sure the current platform can support it safely.
Leadership knows change is needed, but the order, owners, budget, and acceptable risk are still unclear.
Also useful after a leadership change, acquisition, or vendor handoff, before a larger plan is approved.
The Product and Technology Review
A recommendation, the reasoning behind it, and a practical 90-day plan. Delivered in 10 working days, with a leadership readout to agree on the next move.
An illustrative sample, not client work. Your Review is scoped around your decision.
You keep the recommendation and plan. No follow-on engagement required.
Should the team begin a full platform rewrite before committing to enterprise identity and audit controls?
Separate identity and audit responsibilities, test the integration boundary, and measure one release cycle before approving the larger program.
Enterprise identity controls and a reliable audit trail before launch.
Identity and audit responsibilities share an untested boundary.
Name the leader responsible for the decision and the team that will operate it.
What could change the answer? Test failure, rollback, and data behavior before the next commitment.
Name the owners. Document the boundaries. Agree on the test.
Run the smallest complete test. Observe one representative release.
Compare the findings. Choose the next scope, owners, and accepted risks.
Leadership readoutApprove / Narrow / Defer / Stop
Read a sample recommendation and review Jose's current product and platform work at Micr. Both are clearly labeled, and neither is client work.
Current product work
As CTO at Micr, Jose leads product direction, UX, architecture, and infrastructure for an active social gaming product.
Independent recommendation
It may recommend a repair, replacement, focused test, different order of work, or no major investment yet.
We agree on the question, review the relevant facts, test the riskiest assumption, and tell leadership what to do next.
Name the exact question, deadline, business stakes, and person responsible for the final call.
Examine the relevant roadmap, customer requirements, architecture, delivery history, incidents, and responsibilities.
Focus on the unknown most likely to change the recommendation.
Deliver the decision, tradeoffs, owners, checkpoints, and a practical 90-day plan.
Jose Alvarado runs every working session, reviews the evidence, and writes the final recommendation.
Founder, Spanwork Product and platform engineer
Jose is the founder of Spanwork and CTO at Micr. He leads product direction, UX, architecture, and infrastructure for an active software product.
His published work spans social gaming and household product safety, with responsibilities across application systems, data, cloud infrastructure, security, reliability, recovery, and operating cost. That range helps him connect technical choices to delivery, customer commitments, and business risk.
Read how to choose between repair and rewrite, test an enterprise promise, and get stalled roadmap work moving.
The recommendation stands on its own. Any follow-on work is optional and scoped separately.
Typical timeline: 4 to 8 weeks
Test one remaining unknown through a focused prototype, technical investigation, or delivery plan.
Ongoing support
Add part-time technical leadership while the team executes the plan, manages vendors, or hires a permanent lead.
Send the question, the deadline, what is at risk, and what you have already tried. Jose will tell you whether the Review fits.
A short summary is enough. Do not send confidential code, credentials, customer data, or system access through this form.
If there is a fit, the next step is a short conversation. You receive the scope, timeline, deliverables, access requirements, and fixed fee in writing before deciding.
hello@spanwork.net Use the protected inquiry
