A NAMED ENGAGEMENT
A written report on your Rails application, your infrastructure, and the business problem behind them.
Two to three weeks, fixed price, one deliverable. You read the report, then you decide what happens next — whether that is continuing with me, taking the report to your own team, or doing nothing at all.
The point of the review is clarity, not a contract.
WHAT THE REPORT COVERS
- 01Summary for non-technical readers
- 02The business problem, restated
- 03Code base: health, shape, surprises
- 04Infrastructure: what runs where
- 05Risks, ranked by severity
- 06Recommended next steps
- 07Appendix: raw findings, logs, configs
HOW THE THREE WEEKS RUN
Week 1
Kickoff, read-in. One conversation, then I spend the week alone with your code and infrastructure.
Week 2
Deep read. Questions by email, a short mid-point call if useful. Writing begins.
Week 3
Report, walkthrough. You receive the PDF, we meet once to walk through it together.
WHAT HAPPENS AFTER THE REPORT IS YOUR CHOICE
You can continue with me on implementation. You can hand the report to your own developer and act on it internally. You can take it to another consultancy as a brief. Or you can file it and do nothing. Each of those is a reasonable outcome, and the report is written to support all of them.
Ready to begin? I usually start a new review within two to three weeks of a first conversation.