Experienced Bubble.io Developer Needed to Build SaaS-Style Restoration Customer Portal MVP

Project Overview We are looking for an experienced Bubble.io developer / product engineer to help build the first version of a custom customer and operations platform for our growing collectibles restoration business. This is not simply a marketing website or landing page project. We are building a SaaS-style web application that will initially streamline our own restoration operations and customer experience. The immediate priority is building a clean, scalable MVP that allows us to manage the customer journey from: Initial Interest → Evaluation → Quote → Payment → Logistics → Restoration → Progress Updates → Completion → Return / Next Steps We already have a clear product vision, documented workflows, and UI/UX concepts to work from. We are looking for a developer who can help translate this vision into a functional, well-architected Bubble application and provide thoughtful technical input along the way. We are interested in finding a long-term development partner if the initial project is a good fit. About Mintarra Mintarra is a growing collectibles restoration and services business focused primarily on trading cards. Our current business includes: •Restoration services •Customer intake and evaluations •Card logistics •Before-and-after documentation •Grading submission support •Buyback opportunities •Consignment •Collectibles sales •Accessories •Educational content Much of our current customer and operational process is managed manually through: •Forms •Email •Instagram messages •Spreadsheets •Payment platforms •Manual status updates We want to consolidate these processes into a professional, centralized platform that improves efficiency, transparency, and the customer experience. The Broader Mintarra Website The restoration platform will be a core component of the broader Mintarra website rather than a completely separate product. The broader platform will include areas such as: •Home / company overview •About Mintarra •Restoration services •Before-and-after gallery •Shop and collectibles •Accessories •Educational content •Blog and newsletter content •Future courses and digital products The restoration portal should connect naturally to these areas. For example, a user viewing a restoration service or before-and-after gallery should be able to easily begin an evaluation and enter the customer portal. We want the overall experience to feel like one unified Mintarra platform, rather than a disconnected marketing website and separate application. The immediate priority is the restoration workflow and customer portal. However, we want the broader technical architecture considered from the beginning so the platform can grow without requiring a complete rebuild. Initial MVP Scope The first version of the platform will primarily serve Mintarra's own customers and internal team. 1. Customer Intake & Evaluation We want to create a low-friction entry point for potential customers interested in restoration. Potential functionality includes: •Restoration interest/evaluation form •Customer account creation •Image uploads •Card information •Condition/defect information •Customer goals •Requested services •Lead tracking and conversion workflow The goal is to create a smooth process from initial interest through evaluation and conversion. 2. Customer Restoration Portal Customers should have access to a private account and dashboard. The portal should allow customers to view: •Active restoration orders •Current order status •Restoration timeline •Estimated turnaround times •Progress updates •Before/after photos and documentation •Uploaded scans or other records •Messages with the restoration team •Outstanding invoices and payments •Digital agreements and acknowledgments •Next-step recommendations The experience should feel like a modern SaaS customer dashboard rather than a basic form or ecommerce account page. 3. Restoration Workflow The platform should support a structured workflow such as: Evaluation → Quote → Agreement → Payment → Transportation → Received → Intake Documentation → Service Approved → Restoration in Progress → Quality Control → Completed → Return / Pickup → Next Steps Each stage should be trackable internally and, where appropriate, visible to the customer. The goal is to reduce manual updates while still providing customers with meaningful transparency throughout the process. 4. Logistics & Transportation Tracking A major focus of the platform is improving transparency around the movement of customer cards. The system should be able to support different transportation scenarios, including: •Customer shipping •Local pickup •Local drop-off •Show/event handoffs •Third-party or middleman transportation •Return shipping We want to be able to track relevant events such as: •Date and time •Location •Transportation method •Tracking number where applicable •Handler or responsible party •Notes •Confirmation •Photos or documentation where appropriate The goal is to create a clear, understandable timeline for important card movements throughout the restoration process. 5. Messaging & Communication Customers should be able to communicate with the Mintarra team through the platform. Potential functionality includes: •Order-specific messaging •Text messages •Image attachments •Notifications •Read status Messages should be associated with the relevant customer and, where appropriate, a specific restoration order. 6. Digital Documents & Agreements We want to streamline the execution and storage of required documents within the platform. Potential documents include: •Service agreements •Terms and conditions •Risk acknowledgments •Condition documentation •Invoices •Before-and-after records The goal is to reduce unnecessary back-and-forth through separate emails and keep relevant information organized within the customer/order record. 7. Payments & Additional Services We anticipate integrating Stripe or another appropriate payment solution. Potential functionality includes: •Invoice creation •Payment links •Payment status •Additional service recommendations •Customer approval workflows •Additional charges •Refunds or adjustments where applicable For example: A potential additional service is identified → Customer receives an explanation/recommendation → Customer approves or declines → Order and invoice are updated accordingly. 8. Internal Admin & Operations Dashboard We need an internal dashboard to manage the business. This may include: •Leads •New evaluations •Contacted •Evaluation in progress •Quote sent •Converted •Lost •Customers •Customer profiles •Order history •Communication history •Documents •Payment history •Orders •Active restorations •Awaiting customer approval •Awaiting payment •Awaiting shipment •In progress •Quality control •Completed •Logistics •Incoming shipments •In transit •Received •Return shipments •Pickup/drop-off coordination •Payments •Outstanding •Paid •Additional charges •Refunds We are open to recommendations regarding the best structure for the internal operations dashboard. 9. Restoration Team Access Internal team members should be able to access assigned orders based on appropriate permissions. Potential functionality includes: •View assigned work •View service requirements •Upload progress photos •Add progress notes •Update restoration stages •Request additional services •Add internal notes Different user roles should have appropriate access and permissions. Future Expansion The initial MVP will be used by Mintarra internally. The long-term product roadmap may include significant additional functionality, including: •Additional service providers •Expanded service offerings •Vendor profiles •Service comparison •Reviews and reputation systems •Different pricing and turnaround structures •Additional marketplace functionality •AI-powered card analysis and grading tools •Restoration recommendations •ROI/value analysis •Grading submission integrations •Expanded shop and collectibles functionality •Educational content and paid courses We do not expect all of these features to be included in the initial MVP. However, we want the initial database and application architecture designed intelligently enough that the platform can evolve over time without requiring a complete rebuild. Ideal Developer We are looking for someone with experience building actual web applications—not just marketing websites. Ideally, you have experience with: •Bubble.io •SaaS applications •Customer portals •Internal operations dashboards •Marketplace or multi-role applications •Database architecture •Backend workflows •Privacy rules and permissions •Stripe or payment integrations •API integrations •Messaging systems •File and image uploads •Responsive design Experience with marketplaces, logistics, CRM systems, or service-based platforms is a major plus. What We Are Looking For in a Development Partner We are looking for someone who can: •Understand the product beyond simply following instructions •Help us make intelligent technical decisions •Design a scalable database structure •Build reliable workflows and automations •Think through edge cases and operational challenges •Communicate clearly •Identify potential technical issues before they become expensive to fix •Work in structured milestones •Provide realistic estimates •Potentially continue working with us as the platform expands We are not necessarily looking for the lowest-cost developer. We are more interested in finding someone who understands product architecture, can build thoughtfully, and may be interested in a longer-term development relationship. Please Include in Your Proposal To help us evaluate candidates, please provide: 1. Examples of Bubble applications you have built Please prioritize actual functioning applications over simple landing pages. Live links or demonstrable examples are preferred where possible. 2. Have you built a SaaS application or customer portal? If yes, please briefly describe the project and your role. 3. Have you built a marketplace or multi-role application? If yes, please explain the user roles and overall workflow. 4. What is your experience with: •APIs •Stripe/payment systems •File and image storage •Messaging •Backend workflows •Privacy rules and permissions 5. How would you approach the first MVP? Please briefly explain how you would break the project into logical development phases or milestones. 6. How would you think about the core database structure? At a high level, how would you approach relationships between: •Users •Evaluations •Orders •Services •Timeline events •Logistics •Payments •Documents We are not asking for a complete technical architecture in your proposal. We are interested in understanding how you think about the problem. 7. What would you estimate for: •Initial planning/architecture •Development timeline •Development budget •Milestones 8. Are you interested in a longer-term development relationship? Please begin your proposal with “Mintarra MVP” so we know you have read the full project description.