Certainly, how it really works in practice is the real heart of the discussion. I'll offer up a use case of adding a new client. If any of this sounds like hand-waving please ask me to clarify. We have some technologies already in use, and some is still on napkin-diagrams, but all of it is feasible.
ACME design firm won a contract to build a new interactive website for an Event Planning company (Eventus) in PHP. After design discussions they've mocked up an event-planning site that has 4 layouts, 35 static pages, and an additional integrated Event Planning application that allows clients to interactively configure and request pricing for events that Eventus would coordinate.
ACME design firm is partnered with us, and logs into our 'Vendor Admin Console'. They first add a 'New Client', Eventus, and an Admin User from Eventus (first name, last name, email). From there, the system emails the Admin user and allows them to login to our ACME branded site to activate their account, enter in their company info, and manage their own users/permissions.
Next ACME adds a 'New Site' to the Eventus client for the event-planning website. They choose the site type (micro, small, medium, large, dedicated virtual, dedicated, cluster), the billing term (monthly, quarterly, annually), and the price they wish to charge Eventus. They must charge at least our base price, but can add whatever additional margin they wish. After 2x our base price however, we would switch to a flat percentage.
ACME could choose to invoice Eventus directly (not recommended, but some clients insist on paying via check/invoice only), or they could let us handle the automatic recurring billing via CC or eCheck. If we bill Eventus, their site admin receives an email branded from ACME with a link to enter in their billing info/cc/echeck/etc automatically. Every month, we electronically transfer the margin $$$ from all client sites to ACME, and debit any invoice $$$ for client sites that they are invoicing manually. We handle 2nd/3rd notices, account suspensions for non-paying clients automatically as well, but are not responsible for any profits lost from non-paying clients.
ACME can create/review/update/delete Eventus' event-planner website at will, and even add multiple other websites for Eventus. The real goal is for ACME to not ever think about the logistics of Eventus' operations, just to reap the margin rewards, or just the benefit of being a one-stop shop for their clients ongoing needs.
Support is handled through our branded ticketing system. Both ACME and we receive a copy of all support communications with Eventus, and ACME is welcome to field the answers they wish to tackle, while leaving the day-to-day 'how to configure email' questions to us.
Ongoing maintenance/content management for websites will be another optional source of revenue and client-touch for ACME by integrating existing platforms such as the
Osmos CMS. We can also leverage other 3rd party tools with APIs for ecommerce --
Shopify, form-building --
WuFoo, basically anything that we can mashup into the site that will provide value to ACME.
The (small,medium,large) sites would be immediately provisioned and available by proprietary tools we're developing using Amazon EC2 scaling, while the dedicated virtual, dedicated, and cluster/load balanced large application sites would be custom built by our build teams.
The bottom line is that it would live in the shadow of any designer, design firm, or even hosting companies that wanted to seamlessly refer certain types of clients but still get a share in the sales.
Does that begin to answer your questions enough to provide additional feedback?