The short answer
You entirely govern the technical timeline of the software implementation. You do not write free custom code to solve a client's historical data mess. When an enterprise client demands a bespoke data script days before a major launch, they are aggressively attempting to extract unpaid data engineering work from your team to cover their own disorganized records. You must block the scope creep immediately and decisively. State directly that custom script development is entirely outside the standard onboarding scope. Present them with a rigid, uncompromising binary choice. They can format the data themselves to meet your standard import CSV templates, or they can engage your professional services team for a paid, custom engineering project. Do not bend the launch schedule without a signed, highly lucrative change order.
Why this question is a trap
The client is strategically hiding a massive technical liability behind a casual, last-minute request. They know perfectly well that their legacy CRM data is unstructured, corrupted, deeply obsolete, and entirely incompatible with modern systems. They want your internal engineering team to assume the entire risk and the grueling, thankless labor of cleaning it.
If you agree to write a custom script, you completely destroy the onboarding timeline. Custom scripts require rigorous scoping, development, testing, and extensive debugging. When the script inevitably hits data errors in their messy CRM export, your team will be blamed for the resulting delay. You will consume dozens of hours of unpaid engineering bandwidth. The client will expect free custom development for every future technical hurdle, because you proved you will do it for free if they apply enough pressure. You are an Onboarding Specialist, not an on-demand data engineer. You must force the client to pay for custom solutions or do the manual formatting work themselves. Do not subsidize their technical debt with your team's labor.
What most people say
Most Onboarding Specialists desperately want to please enterprise clients and ensure a smooth, celebrated Friday launch. They deeply fear that saying no to a big logo will cause the client to escalate to leadership, complain to sales, or churn before the software is even fully deployed.
They reply with weak, highly destructive accommodations. They say, "Let me check with my engineering team to see if we have bandwidth to write this script quickly for you, but I can't promise anything." They tell the client they will try their absolute best to get it done by Friday to save the launch. This approach is absolutely catastrophic. It immediately commits internal technical resources without securing a single dollar of additional revenue. It signals to the client that the standard implementation boundaries outlined in the contract are entirely fake and fully negotiable. When the engineering team inevitably pushes back on the rushed, unbudgeted request, the Specialist is trapped between a furious internal team and an expectant, demanding client who now feels lied to.
What to say instead
Take absolute control of the technical boundary immediately. You must unilaterally dictate the terms of custom development. Do not leave room for negotiation.
State unequivocally that writing custom ingestion scripts falls entirely outside the standard implementation statement of work they signed. Inform the client that they have exactly two paths forward. Path one: they map their legacy data to the provided CSV templates using their own internal resources, on their own time, to hit the scheduled Friday launch. Path two: you scope a custom engineering project and route it to the professional services team for a formal quote, which will push the launch date out by at least three weeks and cost additional capital. Force them to make a definitive, immediate commercial decision on the call. Do not let them defer the choice.
The phrase to anchor on
The mandatory anchor phrase to use is professional services.
This exact phrase immediately signals that the request requires serious money and a formal contract amendment. It stops the assumption of free labor dead in its tracks. By categorizing their technical demand explicitly under professional services, you move the conversation completely out of standard, included onboarding and into a paid project framework. The client must now decide if their disorganized legacy data is actually worth spending department budget to fix, or if they prefer to do the manual labor themselves.
How to deliver it
Deliver the two strict paths with cold, commercial clarity. Do not apologize for the limitation of the standard software import tools. Do not sound defensive about your engineering team's bandwidth or workload.
Speak with a measured, highly deliberate pace. When outlining path one, emphasize strongly that it requires their own internal resources. When outlining path two, heavily emphasize the phrase professional services and the resulting, unavoidable delay to the launch date. Maintain total silence after presenting the binary choice. Make the client verbalize their commercial decision on the call. Do not jump in to offer a compromise, a discount, or a workaround if they hesitate or complain. They created the messy data problem. They must choose the solution. Your silence forces their hand.
Mistakes that cost you the room
The most dangerous mistake is offering to write a "quick and dirty" script as a one-time favor just to get them across the finish line. There is absolutely no such thing as a quick and dirty script in an enterprise software deployment.
If you deliver a temporary, hacked-together fix, you own the technical debt forever. When the script breaks a month later during a routine sync, the client will furiously demand you fix it immediately because your team built the architecture. You become their permanent, unpaid IT support. Another critical error is negotiating the launch date before securing the signed change order. Do not push the launch date internally until the client has explicitly agreed to the paid professional services route. Protect your internal engineering team at all costs from client chaos and unbudgeted demands.
Practice plan
This drill prepares you for complex technical pushback against highly demanding enterprise clients. Record yourself delivering the rigid binary choice to a simulated client on camera.
Focus intently on the verbal transition between rejecting the free work and offering the paid alternative. Ensure you do not use weak filler words like "unfortunately" or "sorry to say." Practice holding absolute silence after delivering the options. Drill this exact scenario until you can present the commercial reality of custom data engineering without a trace of hesitation, fear, or a desire to please. You are a commercial operator enforcing a contract. Please remember this guide is solely a rehearsal framework for professional communication. Talk Rightly does not provide HR, legal, or technical employment directives.