Loading...
Answers
MenuSetting up an on-demand web services business and quotes very expensive to build the platform from scratch. There should be templates for sale by now?
With so many people creating and developing these complex on-demand websites, we should not be reinventing the wheel anymore. Ive seen the Spotfinder template on wordpress but its more of a catalogue or database, rather than on-demand. Im not a developer and feel that learning code wont help as it would be too complex a job to do properly
Answers
I build API systems daily for myself + clients.
Also other on-demand non-API systems.
To provide you an answer requires a starting point + gathering a good bit of context.
Best if you book calls with me + other people who build this type of software daily.
Tip: Here's how I approach this for myself + clients.
Whatever code I develop, evolves through stages, which self fund the project.
In other words, every month of development must produce income the next month greater than last month's dev cost.
So if month one's estimate is $10K of dev work, this work only starts when there's a clear path to the $10K of work generating $20K of income next month.
My suggestion.
If you can't come up with a clear plan to have income grow fast enough to immediately cover all development cost, get a new idea.
Hint: Most projects I do for myself + clients at this point use a pre sale model.
So, someone (client, myself, many people) market the product at a discount for a small number of users to be in the alpha + beta stages of release.
Sometimes this can generate... well... substantial income...
This also gives a massive window of debugging, where development + debugging costs are covered.
Think of this as a Kickstarter project where money comes in, sometimes for many months or a year at a discount.
So if your service will run $100/month, pre sell a $1200 package for 2-3 years, rather than the normal year of coverage.
To do this you must be clear with participants...
1) There will be problems to wring out of code.
2) You must be clear you can code some sort of product in a few weeks, to provide some sort of deliverable.
3) Don't spend all the money, so you can do instant refunds for participants who loose patience with alpha/beta code quality.
This approach works super well.
There are indeed a number of off the shelf frameworks for the web platform and mobile apps. You should find a few by spending some time. First, identify a mainstream app that's close enough for your concepts like TaskRabbit or dolly or uber. When you are looking for it look for xxx clone script. Make sure the platform is available with source code. Many cases they can fit the platform to your requirement without starting from scratch. That would save around 80% of the development. It might be worth looking for a platform other than WordPress to create scalable platforms.
Look for wordpress plugins, rather than templates.
True, building an on-demand web services platform from scratch can cost you thousands of dollars. You can choose ready to launch or turnkey solutions like YoGigs for building the on-demand services marketplaces at very less cost.
Related Questions
-
What learning path do I have to take to become a "full-stack" web developer?
If I was just starting out, I'd consider learning Meteor (https://www.meteor.com/). It's just entered version 1.0 and after working with it for a little less than a year I do have some issues with it but it still makes for a very solid framework that gets you up and running very fast. You would only need to learn Javascript, and you can slowly work your way towards nodejs from there (which Meteor is based on) if you want to, or you could get the basics down and focus on learning design if you prefer.KD
-
What is the best platform to create a member based CMS website? (e.g. Squarespace)
Most of my friends use www.wordpress.org and http://member.wishlistproducts.com/ to create their membership sites. Hope that helps.DM
-
How can I manage my developers' performance if I don't understand IT?
Whenever you assign them a task, break down the task into small chunks. Make the chunks as small as you can (within reason, and to the extent that your knowledge allows), and tell your devs that if any chunks seem large, that they should further break those chunks down into bite size pieces. For instance, for the overall task of making a new webpage, _you_ might break it down as follows: 1) Set up a database 2) Make a form that takes user email, name, and phone number and adds them to database 3) Have our site send an email to everyone above the age of 50 each week When your devs take a look at it, _they_ might further break down the third step into: A) Set up an email service B) Connect it to the client database C) Figure out how to query the database for certain users D) Have it send emails to users over 50 You can keep using Asana, or you could use something like Trello which might make more sense for a small company, and might be easier to understand and track by yourself. In Trello you'd set up 4 columns titled, "To Do", "Doing", "Ready for Review", "Approved" (or combine the last two into "Done") You might want to tell them to only have tasks in the "Doing" column if they/re actually sitting at their desk working on it. For instance: not to leave a task in "Doing" overnight after work. That way you can actually see what they're working on and how long it takes, but that might be overly micro-manager-y At the end of each day / week when you review the tasks completed, look for ones that took a longer time than average (since, on average, all the tasks should be broken down into sub-tasks of approximately the same difficulty). Ask them about those tasks and why they took longer to do. It may be because they neglected to further break it down into chunks as you had asked (in which case you ask them to do that next time), or it may be that some unexpected snag came up, or it may be a hard task that can't be further broken down. In any case, listen to their explanation and you should be able to tell if it sounds reasonable, and if it sounds fishy, google the problem they say they encountered. You'll be able to get a better feel of their work ethic and honesty by how they answer the question, without worrying as much about what their actual words are. Make sure that when you ask for more details about why a task took longer, you don't do it in a probing way. Make sure they understand that you're doing it for your own learning and to help predict and properly plan future timelines.LV
-
What are the key accomplishments for the first year of a startup?
A generalized question can only get a generalized answer. The most significant accomplishment is validating that the product you have built is a fit with your target market. This is demonstrated primarily by engagement (the people who sign-up or who previously visited, continue to return) and secondarily by growth, ideally based on word-of-mouth or viral growth but effectively converting paid traffic is a great second prize. Other significant accomplishments include: Not running out of money Recruiting and retaining great talent who believe in the founders' vision. Your loved ones not thinking you're as crazy as they thought you were a year ago. I'm happy to talk to you in a call to give you more specifics about what you want to set as your goals more specific to your startup.TW
-
How do you get your first customers for a consulting business?
Back when I started LinkedIn wasn't as huge as it is now. I wish it was. I didn't have a large network and those networking sessions NEVER brought me any clients. I used to go to all sorts of them hoping to get clients. There were a couple of nibbles here and there, but never anything serious. The only thing that helped was reaching out DIRECTLY to people in my target market. That meant cold calls and cold emails. I'd sell myself while thinking about their needs. Once I got a few bites I'd build good rapport by keeping in touch, asking questions, repeating back what they were saying so that they knew I was on the same page and kept my promises. If I said I'd call them back next Tuesday at 2:15 I'd do so. Eventually I built trust with them without having a network, or an insane amount of experience. Oh and the most important thing about consulting is to LISTEN. When those first clients notice that you're truly listening and you're not selling the cookie cutter solutions everyone else is trying to sell them that's when you got them hooked. You start to understand their problems, fears, and see through their eyes and not just yours. A network will help, but in the beginning just good 'ol salesmanship will get the ball rolling.JC
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.