AutoBid Connect Platform Build
Budget: $250 – $750 USD
I am creating AutoBid Connect, a dual-facing solution for dealerships and car shoppers, and I need someone who can shape both the website and the mobile app at the same pace.
Dealership side
The very first release must let dealers log in and quickly post overstock vehicles—vin scan or manual entry—then set a minimum acceptable price and watch offers roll in. From there they should be able to flag specials, flash-sale timers, and aging-inventory tags, but the core workflow is the overstock upload and offer management dashboard.
Customer side
In the app, shoppers must be able to browse inventory from multiple dealers, filter by make, model, year, mileage, price, and location, submit an offer instead of paying sticker, receive push notifications when dealers respond, compare counter-offers side by side, and reserve a car with a deposit.
Scope of this engagement
• UX flowcharts and clickable Figma prototypes for both web and iOS/Android
• A responsive web front end (React, Vue, or similar) plus a cross-platform mobile build (Flutter or React Native) sharing the same REST/GraphQL back end
• Dealer CMS for bulk CSV uploads, VIN decode, photo handling, and minimum-price rules
• Offer engine with real-time alerts, simple negotiation logic, and status tracking
• Basic authentication, role permissions, and Stripe (or comparable) deposit handling
Acceptance criteria
1. A dealer can publish an overstock unit in under two minutes using the CMS.
2. A shopper can locate that unit through filters, place an offer, and see dealer replies in a dedicated “My Offers” screen.
3. All key flows are covered by automated tests and pass in CI.
4. Deployed staging URLs for web and TestFlight/Play Store builds for mobile.
If you have experience launching two-sided marketplaces and can move swiftly from design to an MVP, let’s talk timelines and milestones.
Dealership side
The very first release must let dealers log in and quickly post overstock vehicles—vin scan or manual entry—then set a minimum acceptable price and watch offers roll in. From there they should be able to flag specials, flash-sale timers, and aging-inventory tags, but the core workflow is the overstock upload and offer management dashboard.
Customer side
In the app, shoppers must be able to browse inventory from multiple dealers, filter by make, model, year, mileage, price, and location, submit an offer instead of paying sticker, receive push notifications when dealers respond, compare counter-offers side by side, and reserve a car with a deposit.
Scope of this engagement
• UX flowcharts and clickable Figma prototypes for both web and iOS/Android
• A responsive web front end (React, Vue, or similar) plus a cross-platform mobile build (Flutter or React Native) sharing the same REST/GraphQL back end
• Dealer CMS for bulk CSV uploads, VIN decode, photo handling, and minimum-price rules
• Offer engine with real-time alerts, simple negotiation logic, and status tracking
• Basic authentication, role permissions, and Stripe (or comparable) deposit handling
Acceptance criteria
1. A dealer can publish an overstock unit in under two minutes using the CMS.
2. A shopper can locate that unit through filters, place an offer, and see dealer replies in a dedicated “My Offers” screen.
3. All key flows are covered by automated tests and pass in CI.
4. Deployed staging URLs for web and TestFlight/Play Store builds for mobile.
If you have experience launching two-sided marketplaces and can move swiftly from design to an MVP, let’s talk timelines and milestones.