The idea for this project is to create a vessel for “special projects”, which is a generalizable kind of project which, if successful, can be sold to other companies. Because of the uncertainty surrounding what these products look like, the minimum viable version of this project will only require a few key functions. These include:
Below I will break down the specific requirements of each of these features:
As discussed in the Memberstack piece, my goal for this company is to have it function as a all-purpose vehicle for a collection of “special projects”. These projects are ones that would be costly or overly-complicated for companies to complete in-house. Therefore, the most important aspect of this project will be finding ways to create templated projects which have mass appeal to a variety of potential clients.
For this I’m going to rely on the template pretty heavily. My plan is to customize the design to align with my brand guidelines. Generally speaking though, this template includes all of the things I’d need out of a front-end like:
↳ A landing page (which I’ll need to customize to fit this “special projects” strategy.
↳ An admin-dashboard for me to manage ongoing projects (although they will likely be managed on Notion or Airtable at the very start)
↳ A user dashboard to monitor ongoing projects and to receive deliverables
Because I plan to offer a specific selection of projects (as opposed to any kind of project that the customer might want), I’ll need to switch the flow of how new projects are added (right now it is a text box — I’ll make it into a selection from a list of purchased/all services).
However, for the initial products, I’ll guide the customer through this. Therefore, having the dashboard will be enough — so that the customer can know what ongoing
These projects are going to live somewhere on my website where they can be viewed individually or as a collection. This means I’ll need to create:
↳ A single-product page displaying the name, description, (photos?), (diagrams?) relating to each service, templated via a CMS Collection Page.
⟶ The ability to purchase single services from the page (AND to purchase all services for a flat rate).
↳ A page to display all of the current services (low priority for launch)
The specific requirements of each project will vary. Other software (i.e. Webflow, Make.com, a CMS, or some other client-specific platform) will be incorporated as needed.
There a couple of back-end things that I’ll need to figure out before I can start sending these service pages to clients. Some of these are included in the template from Memberstack, others will need to be customized. These (labeled as such) include:
↳ Logins + user accounts + social auth (all handled by Memberstack)
↳ Project management (handled via CMS + automations)
↳ Payments (handled by the template + Stripe)
Pricing will be a trial and error process where I’ll test how customers react to certain models. There general plan is to:
(1) allow individual services to be purchased for a lower price.
(2) allow for a bundled version of all services (with a 3 per-month limit) to be purchased.
(3) Maybe offer a higher-price, more customizable version of what I’m offering (special requests?)
(1) will be the cheapest, (2) will probably be 2.5(n)x more than (1) (a discount), and (3) will be some multiple more than that. Exact amounts will be tested one potential customers exist.
TBD — will depend on what the final MVP looks like and what I think is “star” of the show. However, I plan to use some automation, some guerilla techniques (calling people, sending physical proposals), and inbound marketing (i.e. posting on Twitter or LinkedIn) to accomplish this.
From this list it seems like the to-do list for this project is: