Rebuild or repair
Determine whether the existing platform can meet the required workflow, performance, and ownership model.
Diagnosis
Make the decision before funding the build.
Architecture reviews, technical audits, and senior engineering advice for founders and CTOs. When you need a CTO without hiring one: fixed-scope engagements with written recommendations for rebuilds, migrations, vendors, and system changes.
Published decision / The Knockturnal
The data said to keep the platform.
A full rebuild was under consideration. The publication was growing, and the audit showed that focused canonical, CSS, image, and caching corrections addressed the material constraints without replacing the whole system.
The recommendation reduced the implementation surface and kept the parts of the platform that were still doing their job.
Read the decision in contextThe artifact
A recommendation another team can act on.
The output is written for implementation, procurement, leadership, and future operators, not only the people in the review meeting.
- 01
Current-state map
The architecture, workflow, ownership, dependencies, evidence, and constraints affecting the decision.
- 02
Options & tradeoffs
Viable paths compared against risk, operating cost, maintainability, client ownership, and implementation dependency.
- 03
Written recommendation
A specific decision, the evidence behind it, material uncertainty, and the conditions that would change the answer.
- 04
Implementation roadmap
Ordered work, validation criteria, access requirements, and ownership boundaries that another team can execute.
Decision types
Use diagnosis where the next commitment is still unclear.
Migrate or consolidate
Map estate risk, content, integrations, cutover constraints, and the target operating model.
Buy, configure, or build
Compare an existing product with custom implementation against the differentiating workflow and integration cost.
Keep or replace a vendor
Evaluate the current delivery, technical constraints, ownership, and the transition cost of changing partners.
Review method
Frame, inspect, compare, recommend.
-
Frame the decision
Name the commitment being considered, the evidence required, the stakeholders, and the consequence of being wrong.
-
Inspect the environment
Review the relevant code, platform, content, data, integrations, analytics, workflow, access, and vendor constraints.
-
Compare viable paths
Document tradeoffs and dependencies using the same operating and validation criteria for each option.
-
Deliver the recommendation
Provide the decision, evidence, uncertainty, ordered roadmap, and artifacts an implementation team can use.
Wrong fit
If the decision and scope are already clear, move into implementation.
Consulting should reduce uncertainty that changes a material commitment. It should not add a report between a team and work it already understands how to execute.
Questions
Technical consulting questions, answered.
The engagement is scoped around a decision and a written artifact, not an ongoing executive role.
Get the diagnosis before the commitment