Software Company Ltd
- Product A
- Product B
Vs.
Scenario B:
Product A Ltd
Product B Ltd
Scenario A Advantages:
- simpler accounting and reduced costs: only needing to pay for services like Bank Accounts and Liability Insurance once.
- can easily create new products and sell them without having to register another company and buying all the required services again.
Scenario B Advantages:
- less Risk from liability, i.e. if someone sues and brings down Product A Ltd, Product B Ltd can continue to run unaffected, whereas in Scenario A both product businesses would be liquidated.
- if deciding to sell off or close down one product, I could benefit from entreprenurial relief when winding down that business, making it much more tax efficient.
I'm a soloprenuer hoping to startup my first SAAS product soon, and I was originally leaning towards Scenario A. However after some thought, I think because my first product is going to take up so much of my time over the next year or two, it's unlikely i'll launch any other products, and the product im building holds some personal data so I think i'd want to reduce the future liability risk.
Any thoughts from anyone on these two approaches to building software businesses? Anything i've overlooked?
1. Linked images 2. Cid images (images are attached) 3. Base64 encoded images
My gut says to stick to linked images for simplicity and ensure the image title tags are descriptive. At work we use cid images as they seem to show up more often during testing.
Any recommendations?
So, my first thought would be a Dell U2417H as it's the latest ultrasharp in the resolution/aspect ratio. However, is it worth looking at any other devices? Maybe something with 144hz?
I've worked with angular and i really like the data-driven approach, though angular doesn't play nice with jquery and you need another library on top of it to work with bootstrap, which is apparently feature incomplete. I've looked at vuejs, and because of the virtual DOM, it doesn't go well with libraries that manipulate the real DOM directly. The solution to this is to get modified vue-friendly versions of libraries, which is a road im not keen to go down. React seems like it has similar problems.
Is there any js framework that plays nice with bootstrap and jquery and would be better to work with than pure jquery?
The reason I thought of doing this is in case a support request coming through along the lines of "i deleted this by mistake, please help". In this case, changing a field in the table would be much easier than restoring a backup and then writing a script to put the data back into the live database.
Is this a good approach? An alternative to having a delete flag would be moving records to a deletion table, but that seems more work. Obviously, if a client doesn't request a deleted record to be restored after a certain period of time, the record can actually be deleted (via an automated process).
However, it's a worry for many people (myself included) that disclosing a non-tech product, which are often much easier to replicate (bingo card creator for example) to a tech audience might encourage unwanted competition.
I'm planning to redesign my personal website and blog more in the near future, and i'm wondering about mentioning my B2B SAAS startup, or whether to partially hide it away in my LinkedIn/Offline CV.
Do you disclose your non-tech businesses on your website/public social media accounts?
When someone types "Big Example Software" I want to be the number one result in search engines. I currently have both bigexamplesoftware.com and bigexample.software. I think prefer the .software domain extension as it looks neater, but will it harm my efforts to be the number one result? Any other downsides to it?
Unfortunately the equivalent of bigexample.com is taken, as that'd be the best of both worlds.