ROI for Custom Software

[Magma]

My thought (not always right) :

Don't think so much of about such perfect idea will come out.

I believe many successful businesses are not come from a great idea.

The founders may came out with an idea which is not obvious.

It may seems not interesting or anyone can get it.

This also caused not many people will even want to invest on it in early stage.

With perseverance, the founder will keeping fine tune the product.

It is until certain versions when the product is starting to show something the public can see the usefulness.

So I can say, stick to something we are already familiar with. It is less risky and we can sure we can do it very well.

In the meantime, a problem will suddenly float up and this is the opportunity to provide a solution.

Sometimes a "product" or "service" is condemned... hope the best for your products and ideas general...
and Sometimes the same product ...comes... the most wanted... from nowhere...

Sometimes Keys / Marketing can also help a product.. can be a simple or something that someone can find it and may be find a better version from other developers... but yours can have the best "Name" / key ever.. and downloaded by Millions...

Also something... I ve seen all years I am having my own business... is that you can have 99.99% failures... and when the 0.01% you can make your turn... but need careful moves every time...

 

[aeric]

Well, try your best to think positively.
Of course I am not saying we don't consider bad thing can happen.
Think of a plan B if it really happen.
Most likely, it is not a big deal.
Just focus on your objective.
If you feel lost in the middle of road, think back why you decided to take this route when started.
You believed on something beautiful in the other side.
It just this time is not your turn yet.
If it happens that your turn is tomorrow and you give up today after working hard for years, then what a pity?
Like the old saying of Jack Ma.
Today is hard, tomorrow is even worse ...
(You can Google it yourself)

So, it's your baby. You want to see it fails? I am sure you will do something or all you can to protect what you believed.

 

[aeric]

Today is difficult, tomorrow is much more difficult, but the day after tomorrow is beautiful. Most people die tomorrow evening. - Jack Ma

74 Jack Ma Quotes on Success (ALIBABA)

Also read…

graciousquotes.com

 

[Magma]

 

[aeric]

Beware of some fake AI generated video.

 

[aeric]

I would not consider myself to be "rich". I have more than enough to retire and do whatever I want, wherever I want and still pass down to my family. That's all I ever wanted and need.

Yes, custom programming. I sold my first custom piece of software at 16. Took a break to go to college (unrelated) and then returned to programming to form a company. Sold that to a Hong Kong company that took the software/solution to South America. Started another software/IT company and then another with engineers until a few years ago. Retired then unretired and started 2 more companies that are still running. Also, got involved with a nonprofit on the science IT side of things that I find very rewarding. I have to say that all of this is NOT just me. Lots of partners and others involved.

The "secret" which hasn't been a secret for, probably, many millenia and is in my previous post .... "Find a need. Fill a need" is really all it boils down to. Oh, and choosing a profitable (money-wise, soul, community, in any combination you deem worthy) need to fill I guess would be the deciding parameter there. I'm not about to custom-make a POS type of application to try to compete with the multitudes of them out there, for example. I don't care how fast, cheap or wonderful the interface is; it's not going to be rewarding for me or my business.

One of my pet peeves, when it comes to hiring employees and when I hear these kinds of complaints from developers or programmers is the inflexibility. I was taught as a child, in a fairly poor, rural area to poor family that, literally, dug ditches and got very dirty for a living (ie, dig and eat, rest and don't), that you did the work for which work there was. Meaning, when I look at a new programming project, or business problem/solution I've been asked about or just found on my own, I don't, first, look at my own tools/skills/experience to decide how I'm going to tackle it. If I have that "tool" in my toolchest to solve the problem in the best way, then I'll use it. If not, then I quickly pivot to either find or simply make that tool. Work the problem in front of you; not the tool in your hand. Far too many programmers, to bring it back to somewhere close to this forum, only see their tool (programming language? experience? comfort-zone?) to solve the problem. Same goes for developers on the wider-view of the world around them and the opportunities therein. Find the problem. Fix the problem. Simple.

Are you interested to get interview to share your points? On a podcast session.
May benefit to some young entrepreneurs who are still struggling in the business.

 

[brad07226]

When it comes to ROI for custom software, partnering with the right dev team makes all the difference — and that’s where Techstack comes in. They focus not just on building functional products, but on aligning every feature with your business goals. That means fewer unnecessary add-ons, faster delivery, and real value over time. If you’re investing in custom software to boost efficiency, automate tasks, or scale smarter, Techstack helps make sure that investment actually pays off.

 

[HotShoe]

ROI is irrelevant in contract programming. Just my opinion of course, but if you are not getting paid enough for your efforts, then you are not quoting enough and cutting your own throat. You have to know when to walk away from a request for quote, or during negotiations for that matter. Get all of that out of the way before you sign the contract. ROI is no where in that calculation for the contract programmer.

Oh and howdy guys

--- Jem

 

[aeric]

Many people don't read what I wrote.
I am talking about calculating the ROI for clients, not for ourselves.

 

[HotShoe]

You're right, my mistake. I write business software, so the ROI for the client is always better productivity. Designing a better, quicker way to do the day to day jobs that they need the software to do. My job is to take their idea and create a better way to implement a fast interface for the user or more efficient back end to handle the data, or both. So it's not a straight forward calculation in terms of cash, or even of time. Each user (employee) will have their own learning curve and will work at their own pace.

So for my business model at least, I am not writing a program that will be sold to others, but specific and highly customized solutions for a particular business/industry. Calculating and ROI based upon peoples performance is not something I do. I can show the benefits of my design to the client though. If not, I have failed and will probably end up in court.

--- Jem

 

[Peter Simpson]

Howdy HS,
Long time no hear from.

Oh and howdy guys

It's extremely nice to see you on the forum again, it's great to know that you're alive and kicking.
Stay safe and well.

I do agree with @HotShoe, I've walked away from potentially new clients because I already give more than competitive prices for bespoke project, and I never ever drop by price once given on a proposal document, never.

Many people don't read what I wrote.

I have read exactly what you said, I'm just agreeing with HS on what he said.

Sorry @aeric, this thread is all yours again.


Enjoy...