A support team needs an assistant that replies in their company's specific tone and terminology by tomorrow morning. They have only 300 example tickets showing that tone, and cannot spend several days on a training and evaluation cycle. What is the most appropriate first approach in Foundry?

The correct answer is D. Placing a handful of representative examples of the desired tone directly in the system message lets the base model imitate that style immediately, with no training pipeline, evaluation cycle, or waiting period, which fits both the tight deadline and the modest example count. Option A is incorrect because fine-tuning involves preparing a training job, running it, and evaluating the resulting model before it can be trusted in production, a process that reliably takes longer than one day even with only 300 examples. Option B is incorrect because waiting for 10,000 examples abandons the deadline entirely and is unnecessary; few-shot prompting can demonstrate a tone convincingly with far fewer samples than a fine-tuning job would need to be worthwhile. Option C is incorrect because training a new model architecture from scratch requires vastly more data, compute, and time than either fine-tuning or prompting, and is never appropriate for a same-day turnaround. When time is short and the goal is stylistic imitation rather than teaching new facts or complex behavior, few-shot examples in the prompt are the fastest lever available in Foundry, with fine-tuning reserved for cases where prompting has been tried and still falls short.