Prepare
What to prepare before a Morrow Assessment.
This page exists to make the front door more useful. You do not need perfect documentation. You do need enough truth about the product, the technical unease, and the current business pressure for good judgment to happen quickly.
A real product, internal tool, or revenue-critical system that already matters — but currently feels structurally uneasy.
Reducing vague inquiries, improving assessment speed, and making the first conversation feel more like an operator process than a generic contact step.
Messy inputs are normal. Hidden reality is the problem, not imperfect packaging.
Bring these 5 things
A short explanation of what the product does, who depends on it, and why this situation matters now.
A live URL, staging link, screenshots, or Loom showing the core flow and where confidence starts to break.
Stack, hosting, auth, billing, data model, deployment reality, and which areas feel expensive or scary to touch.
What is forcing clarity now: launch risk, customer promises, team bottlenecks, support load, roadmap drag, or revenue pressure.
What can actually be reviewed today: repo, logs, dashboards, docs, screen share, or only the live product and a demo.
The weird edge cases, recurring support fires, or systems everyone is afraid to change. Those clues are usually useful.
Artifacts that help most
You do not need a clean handoff. You do need enough surface area to inspect reality.
- Live and staging URLs if both exist
- A Loom or short walkthrough of the important user journey
- Known integrations: auth, payments, email, AI providers, storage, analytics, jobs
- Notes on what has already broken, regressed, or slipped
- Current milestone, deadline, or commercial pressure
- Honest access constraints and decision-maker availability
If access is messy
That is normal. Morrow Works can still often start with a demo, screenshots, architecture notes, and a truthful explanation of what is and is not accessible yet.
If the repo is off-limits
The assessment can still be useful, but the recommendation will be narrower and more conditional because less technical reality can be verified directly.
Prep workbench
Turn scattered product context into one clean assessment brief.
Use this worksheet to gather the facts that usually make a Morrow inquiry sharper to review. Your notes stay in this browser unless you explicitly copy or download them.
Best use: spend 5–10 minutes here, copy the brief, then paste the useful parts into the inquiry form or share it with your internal decision-maker.
- Reduces vague inquiries and missing links
- Makes the expensive subsystem or risky path easier to name clearly
- Creates a reusable internal brief before anyone opens a larger engagement
See whether you have enough signal to open the assessment inquiry.
Morrow Works does not need perfect documentation, but strong inquiries usually include all six inputs below.
- Add a few details and the missing items will appear here.
This assembles your notes into one operator-style summary you can paste into the inquiry form or share internally before the engagement decision.
Fill in the worksheet and your assessment brief will appear here.
Questions to answer before you inquire
- What does the product actually do today?
- What part is already valuable or traction-bearing?
- What part would make the team nervous in front of more users or more revenue?
- Which subsystem feels most structurally uneasy?
- What is hardest to change without collateral damage?
- What still depends too much on memory or heroic behavior?
- What needs to be true in the next 30–90 days?
- What gets more expensive if nothing improves?
- Are you open to hearing that some part of the current path should stop being preserved?
What happens after submission
- Morrow Works reviews the inquiry for fit, pressure level, access reality, and whether the technical decision surface is real.
- Strong fits usually begin with the $2,500 Morrow Assessment.
- If the risk is already narrow and obvious, the next conversation may move directly into a scoped Morrow Rescue.
- If the product needs steadier support after diagnosis, the assessment can become the entry point into Build Partner work.
- If it is too early, too broad, or not a fit, that should become clear quickly.
Ready
Bring the messy truth, not the polished story.
The assessment works best when the real product, the real technical unease, and the real commercial pressure are visible early.
Start there if you want the actual intake path. Read the assessment page first if you want scope and deliverables.