The Small Fish in a Big Pond: Working with Large Clients
summary
A practical checklist: use a one‑page quad chart not a 15‑page proposal; expect vendor onboarding, a 40‑page security questionnaire, and an MSA that decides code ownership; plan for net 60 or net 90 payments and make an early, easy deliverable so invoices start flowing; estimate hours, log time honestly (a CMS feature that felt like 2–3 days actually took 5–6); pick risky tasks first, run one‑day experiments, track progress with an assembl burndown, and verify fixes (eg push notification delivery bug) before you ship.
AI-written summary · about
chapters (39)
- 0:00Introduction
- 3:53How do we support people
- 4:16Roadmap
- 5:12Quadchart
- 7:08Minimum Viable Product
- 8:51Expect Some Red Tape
- 10:17Master Service Agreement
- 11:07Security Assessment
- 11:49Contingency Plans
- 12:32Pace Yourself
- 14:10Create a Contract
- 15:23Identify Risks
- 16:33Plan Deliverables
- 17:23Net 60
- 18:09Start working
- 18:29Plan everything together
- 20:35Avoid scope creep
- 22:51Are you headed in the right direction
- 23:09What are your experiments
- 24:14Its time to invest
- 24:32Commit to solve the problem
- 25:48Log your time and deliverable
- 26:12Live out your time
- 29:24Burndown chart
- 30:07Things are burning down
- 30:34Things need to change
- 31:55Avoid entering survival mode
- 32:18Dont be controlled by your todo list
- 34:08Produce accurate documentation
- 34:55Push notifications
- 36:09Provide accurate documentation
- 37:09Deliver on milestones
- 37:22Deliver on time
- 38:29Revision cycles
- 38:39No signing off with changes
- 39:23Wrapping things up
- 39:36Preparing for change
- 42:16Customer feedback
- 43:12Conclusion
