Custom projects fail in the quotation stage more often than in the engineering stage, and the failure is symmetric: the buyer sends a sentence — "we want a smart sensor with our brand, similar to yours but better" — and expects a number; the factory replies with a brochure because the sentence contains no information a number could attach to. The fix is an input checklist. Both sides can produce it in a day, and it converts the conversation from mood to engineering.
The seven inputs that make a quotation possible
First, the target: which product category, and the closest existing reference — "a PIR sensor like a standard dome unit, but Zigbee with a two-year battery claim" is a spec; "a smart sensor" is a wish. The reference anchors every later trade-off.
Second, the destination market, because it decides certification, radio bands, plug standards and app infrastructure before a single line is drawn. A product for the EU and a product for Russia are different projects that happen to share a housing.
Third, the quantity expectation, stated honestly. A 2,000-piece project and a 50,000-piece project justify different tooling, and a factory quoting the former with the latter's assumptions will either lose money or quote high enough to lose the deal.
Fourth, the differentiation list, ranked. Not "different from competitors" but which three things must be true that the reference product does not do. A ranked list lets the factory protect the top item when budget pressure arrives — and budget pressure always arrives.
Fifth, the brand surface: logo placement, packaging, app naming, and whether the app is the factory's white-label cloud or the buyer's own. The app answer alone can swing the timeline by months.
Sixth, the certification requirement: which marks, who holds them, and whether existing family certificates can be extended to the variant. Certification is a schedule, not a checkbox.
Seventh, the launch date with the reason behind it. A retail window, a trade show, a funding milestone — the reason changes what the factory is allowed to trade away when the schedule slips, and knowing which compromises are acceptable is worth more than any schedule chart.
What the factory should send back
The checklist works both directions. A serious factory responds to a complete input set with three documents: a technical feasibility note naming the risks in plain language, a phased quotation — development or configuration fee, tooling, then unit price at the stated quantities — and a schedule with the dependencies visible, certification and tooling time being the two that cannot be compressed by enthusiasm. A response that is a single unit price with no phases has not answered the project; it has answered the sample request, which is a different question.
The conversation the checklist enables
With inputs defined, the productive negotiation becomes possible: which requirements drive tooling, which certification path fits the schedule, where a stock platform absorbs a custom request for free, and where a "small change" carries a mould. Buyers are often surprised how much of their wish list lands at no tooling cost — a different LED indicator, a firmware default, a packaging variant — once someone separates the requirements that touch steel from the ones that touch software.
XingLiao runs custom smart home development with this input checklist as the entry point — feasibility, phased quotation and schedule against the seven inputs — and backs the programmes with the manufacturing side at xingliaotech.com.
The short version
A custom project is quoted against information, not enthusiasm. Category and reference, market, quantity, ranked differentiation, brand surface, certification, launch date — seven inputs, one day of work, and the difference between a number that means something and a brochure that means nothing.
Top comments (0)