liveBook · Manning

Roadmap signal

As explained in Crack Any Codebase with AI

A roadmap signal is partially implemented code or configuration that indicates an unannounced or unfinished product direction.

A roadmap signal is partially implemented code or configuration that points to an unfinished or unannounced product direction. Treat empty configuration slots, stub database tables, and lightly used queues as committed infrastructure—not promises from marketing. section 5.5

Cal.com's poured concrete

Cal.com exposes an empty DAILY_API_KEY slot, a half-built tasker queue, and a Team table with many added columns. Together, these artifacts suggest investment in capabilities not yet fully shipped. The Agent and CalAiPhoneNumber models sharpen the inference: scheduling is moving toward automated calls that confirm, gather information, or reschedule meetings. section 5.5

What's surprisingly present
What's hiding in the code
The bet it reveals
The schema declares an Agent and a CalAiPhoneNumber model (packages/prisma/schema.prisma), plus a create-phone-call endpoint in the v2 API: an AI agent that makes outbound phone calls to book meetings. If a customer who scheduled a sales demo goes silent in the days before the call, Cal.com dials their actual phone number and has an AI voice talk to them, confirming attendance, gathering information, even rescheduling on the fly. For a product most people picture as a button you click to pick a time, this is a quietly massive expansion of what the company thinks scheduling is.
Voice will replace booking forms. The future of scheduling isn't a prettier form on a webpage; it's an automated agent that calls, texts, and follows up until the meeting actually happens. Scheduling stops being passive calendar math and becomes something that reaches out to humans on its own.

Use the artifact-to-bet table to connect hidden implementation details with the product direction they imply. section 5.5

How Crack Any Codebase with AI covers it

How deep it goes
Explains the heuristic through configuration, schema, and queue examples without tracing implementation history.
Examples
Uses DAILY_API_KEY, the tasker queue, Team columns, Agent, and CalAiPhoneNumber as signals in Cal.com.
What you can do after
Evaluate product direction by translating unfinished code and configuration into explicit strategic bets.
How it connects
Connects product strategy with codebase analysis, database schema, configuration, worker queues, and deliberate constraints.

This explainer was generated by Manning's knowledge graph from the text of Crack Any Codebase with AI. The section links point to the parts of the book it draws on.