FIELD NOTE / INSTAGRAM
Your new internal tool has a second year.
The complete written thought and the evidence behind it. The video edition will follow its public release.
The written argument is here.
This approved Instagram edition is on the journal now. Its video player and original platform link will appear after each public release is verified.
Your new internal tool has a second year.
Video caption
Your new internal tool has a second year.
Include the work users never see.
A custom workflow may still be justified.
Buy, compose or build on purpose.
#EricFieldNotes
Full written post / accessibility read
Claude Code can help someone build a calendar tool quickly. Now carry that tool into next year. A customer reschedules across time zones, a reminder fails, an employee leaves and an integration changes. The question is not whether the first screen works; it is who restores the business process.
Draw four columns: implementation, integration, operation and eventual replacement. Add authentication, permissions, monitoring, cancellations, data export and the maker's time away from their role. Compare that with a maintained SaaS plan and its own integration limits. Do not hide either side's costs.
If a company needs an unusual handoff or regulated data boundary, prototype that requirement against real maintained tools. If no product can meet it, specify the custom boundary and named maintenance owner. Sometimes the best architecture is a bought scheduler with one carefully owned bridge.
Use the smallest maintained system that satisfies the business contract, then custom-build only the part that creates durable advantage. Do this because every extra generated feature becomes a promise your team must keep after the person who prompted it moves on.
#EricFieldNotes
Four-beat scene transcript
1. Your new internal tool has a second year.
Claude Code can help someone build a calendar tool quickly. Now carry that tool into next year. A customer reschedules across time zones, a reminder fails, an employee leaves and an integration changes. The question is not whether the first screen works; it is who restores the business process.
Visual: The demo is only month zero.
2. Price the responsibility timeline.
Draw four columns: implementation, integration, operation and eventual replacement. Add authentication, permissions, monitoring, cancellations, data export and the maker's time away from their role. Compare that with a maintained SaaS plan and its own integration limits. Do not hide either side's costs.
Visual: Include the work users never see.
3. Find the actual differentiator.
If a company needs an unusual handoff or regulated data boundary, prototype that requirement against real maintained tools. If no product can meet it, specify the custom boundary and named maintenance owner. Sometimes the best architecture is a bought scheduler with one carefully owned bridge.
Visual: A custom workflow may still be justified.
4. Choose the least ownership that works.
Use the smallest maintained system that satisfies the business contract, then custom-build only the part that creates durable advantage. Do this because every extra generated feature becomes a promise your team must keep after the person who prompted it moves on.
Visual: Buy, compose or build on purpose.
Research and claim limits
- Claude Code overview (S48)
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.