I've been freelancing for a couple of months and been thinking of starting a traditional no-code agency. But I recently came across productized services and it seems a better approach to doing thing.
However I really cannot wrap my head around on how to standardize app development? I cannot tell a client that we'll integrate only these X Y Z features and nothing else.
Although most of the app on the internet can be broadly categorized into a handful of categories like CRM, marketplace, ecommerce etc, there is still a lot of customization that needs to be done for every project.
Someone suggested that I should use these categories and standardize the customization that we'll do. This seems a good start but I just want to know what you think about it.
A productized development example - https://devondemand.co/ but they focus primarily on the front end part. I could do a similar thing and productize the front end and keep the backend part as custom development.
What do you think?
Hey Himanshu!
I’ve been scratching my head over your problem for years at my previous agency (a "yes-code" software house). I’ve tried many different packages over the years, based on pages, number of platforms, modules to integrate with, etc. After 12 years, we settled on selling sprints (and that works pretty well, FWIW).
It is difficult to standardize deliverables when 1) the very essence of what you do is custom, and 2) the commitment of your customer in their role has a big influence in the success of the project. Most agency "gurus" recommend value-based pricing over hourly fees, which makes total sense but I've always felt that difficult to apply to software development (and I've consulted said gurus).
Something you can do is standardize your methodology/processes and guarantee "best possible results in allocated time and cost“ (see the famous “project management triangle”). This is what agencies do when they sell workshops, design sprints, etc. : they commit on a methodology and agreed time/cost constraints.
I remember seeing that Dev on Demand page on @Vinrob’s FB group and I will admit I was pretty doubtful, because for me “page” is not a work unit that makes sense for modern web development. Or the word “development” is just not meant the way I use it as a software engineer ;) But judging from Product Hunt, they seem to be doing fine, so I’m definitely curious too!
Happy to discuss this further because even though I’m on a new venture now, it’s a problem I’m still pretty passionate about!
Nicolas
Yes agree with the rest that doing a productized service for all nocode is too broad. It's better to niche down. Some nocode agencies just focus on ONE tool, like a Zapier automation agency, or a Webflow design agency. Others focus on the task, like landing pages using Google Sheets. Niche down first then expand your offerings later when your customers demand for it. Also great to start off with finding a few customers first, build ing stuff for them and at same time getting their feedback. You'll learn a lot about what kind of nocode productized service to launch that way
Yeah, I agree that I need to stick to one tool. We only build with Bubble.
I guess I'll talk to our current customers and see what they want.
Interesting idea Himanshu. I looked at devondemand and it seems quite niche in their offering.
When we start to think of nocode development as a productized service, it may be too broad a definition. Have you thought of offering the productized service in one type of app? For example, just in the CRM space. This may narrow the field a bit.
Definitely agree with @jacobeus that productizing one sprint may be an option. However that requires building trust with clients so they are confident of getting value from the sprint.