Websites, RFQ Forms and CRM Pipelines for Manufacturers
Manufacturers who are choosing a web partner often check the same five things: wireframe approval, a CRM that tracks each RFQ, ownership terms, how uploaded drawings are kept, and whether the build cost is separate from monthly fees. This page answers each one in AppWT's own words, with a link to the page that backs it up.
Who this page is for
Owners, plant managers and sales leads at manufacturers, job shops and industrial suppliers who want a website that brings in requests for quote (RFQs) and a system that tracks each one until it is won or lost. AppWT works remotely with manufacturers across the United States, including North Carolina and West Michigan, from its headquarters in Livonia, Michigan.
The buyer's checklist, answered
-
Wireframe approval before the build
AppWT wireframes the public pages, the RFQ form and the back-end screens first. You approve the layout and the flow before design or code begins.
Wireframes and clickable prototypes are agreed before any code is written, so the build starts from a plan both sides have signed off.
-
A CRM that moves an RFQ through stages
Every RFQ sent from your website lands in AppWT CRM as a lead, with the page and source that produced it.
The lead sits on a pipeline board whose stages your team names, for example received, quoting, quote sent, won and lost. Stages can be marked as won or lost, and the board shows how many leads sit in each stage and their total value.
The CRM also times how long your team took to first call, text or email the buyer. Opening or dragging a card does not stop that clock.
-
Who owns the code, the data and the exports
Ownership of the code is set in each project agreement, and AppWT keeps its own pre-existing tools and frameworks. Source is delivered as readable files in PHP, JavaScript, HTML, CSS and SQL, not locked inside a page builder.
AppWT CRM is a hosted account on software AppWT runs. The AppWT CRM page explains who owns what, what you can export and what happens if you leave, so read it before you sign.
-
Security for uploaded drawings
appwt.com and AppWT CRM answer only over HTTPS. A plain HTTP request is redirected, the servers accept TLS 1.2 and TLS 1.3, and browsers are told to use HTTPS for a full year.
When your team attaches a drawing to a lead in AppWT CRM, the file is stored outside the public web folder, in a folder only the server account can open. Each file is saved under a random name, the original file name is kept only as a label, and the file gets a SHA-256 fingerprint. A file is served only to a signed-in user of the same account.
Files are limited to 20 MB each. The CRM accepts PDF, image, Word, Excel, text and CSV files today, so a drawing goes in as a PDF or an image. The RFQ form on your own website is wireframed first, so if your buyers send native CAD files, or a drawing is export-controlled or under a customer NDA, raise it then and settle which files the form accepts and where they are kept before the build starts.
-
Build cost kept separate from monthly fees
The AppWT pricing page lists website builds as one-time project tiers. Hosting, care and AI search visibility work are listed separately as monthly plans.
Ask for the build and each monthly item as separate lines in your written quote, so you can compare them line by line.
How a manufacturing project runs
- Consultation. A free 60-minute consultation by phone or video. It covers scope, pricing, timeline and a written quote, with no commitment.
- Discovery. AppWT works with your engineering and sales team to describe your processes, materials, equipment and certifications accurately, and lists the systems the website has to talk to.
- Wireframes, your first approval. You approve the page layout, the RFQ form and the back-end screens before design or code begins.
- Build on a staging site, your second approval. The site is built on a staging site you click through before launch, so you can check every page and form before it goes live.
- Launch. Each RFQ lands in the CRM as a lead with its source, and your team works it through the stages you named.
Timeline. Launch dates are set per project, and they depend on how quickly content and approvals come back from you. The 6-hour delivery times on the AppWT home page are measured on standard informative websites built from AppWT's own library of tested modules. A manufacturing build with an RFQ form, a CRM pipeline and connections to your other systems is scheduled in its own written scope.
What custom means here
The code is written for your project in readable PHP, JavaScript, HTML, CSS and SQL, using AppWT's own tested modules where they fit, and it is not built in a page builder. Your capability pages, RFQ form, CRM stages and any customer sign-in area are planned in your wireframes, not picked from a catalog.
Where AppWT works, and where it meets in person
AppWT's headquarters is in Livonia, Michigan. Projects for manufacturers in North Carolina, West Michigan and the rest of the United States run remotely, on video calls, shared wireframes and a staging site you click through before launch.
Free on-site consultations cover Oakland, Wayne and Washtenaw counties in Michigan. Outside those three counties, travel is available, and AppWT discloses any travel fee before you book.
Proof and case studies
AppWT's automation and integration work is described on the industrial automation page. Several of those engagements are covered by a mutual non-disclosure agreement, so they are described there as capability rather than by name. Published client results are on the case studies page.
Questions manufacturers ask
Does AppWT get wireframe approval before it builds a manufacturer's website?
Yes. AppWT wireframes the public pages, the RFQ form and the back-end screens first, and you approve the layout and the flow before design or code begins.
Can AppWT CRM track an RFQ through pipeline stages?
Yes. Each website RFQ lands in AppWT CRM as a lead with its page and source. It moves across a pipeline board with stages your team names, including won and lost, and the board shows the count and total value in each stage.
Who owns the code when AppWT builds a manufacturer's website?
Ownership of the code is set in each project agreement, and AppWT keeps its own pre-existing tools and frameworks. The source is delivered as readable PHP, JavaScript, HTML, CSS and SQL files. For the hosted AppWT CRM, the AppWT CRM page explains who owns what, what you can export and what happens if you leave.
How are drawings stored in AppWT CRM?
A drawing attached to a lead in AppWT CRM is stored outside the public web folder under a random file name, in a folder only the server account can open, and is served only to signed-in users of the same account. Files are limited to 20 MB, and drawings go in as PDF or image files today.
Does AppWT work with manufacturers outside Michigan?
Yes. AppWT works remotely with manufacturers across the United States, including North Carolina and West Michigan, from its headquarters in Livonia, Michigan. Projects run on video calls, shared wireframes and a staging site you click through before launch.
Are build costs separate from monthly fees at AppWT?
Yes. The AppWT pricing page lists website builds as one-time project tiers and lists hosting, care and AI search visibility work as separate monthly plans.
Start with your RFQ process
Bring your current website, the way RFQs reach your team today and the systems the site has to talk to. The consultation covers scope, pricing, timeline and a written quote, with no commitment.
AppWT Web & AI Solutions (AppWT LLC). 29+ years of practice. Operating as AppWT since 2005, and formed in Michigan as AppWT LLC in 2020. BBB A+ accredited since 2022. Calls, texts and email are answered 24 hours a day, every day of the year.
