> Our two biggest competitors are internal development teams (who end up being stuck doing this kind of work) and consultants (who charge a ton of money.)
But this is still consultancy work, right? So the differentiator here is managing those integrations like a real software company and thus cutting costs?
If Hotswap learns how to migrate from company/technology A for client B, they can save time when helping client C if they also need to migrate data from company/technology A
In my experience, working with consultancies, they are not engineering first organizations. They are business types who have bolted on engineering (think legacy automakers bolting together binned products), instead of organically turbocharging their growth through automation and software engineering best practices (think Tesla vertically integrating and "building the machine that builds the machine").
If you're an MBA or biz type, you want to be at the former. If you're an engineer, you want to be at the latter.
Why would it be consultancy? They only need to write e.g. the Wix-extraction code once hopefully, and then just run it for each new client. Seems very scalable.
But this is still consultancy work, right? So the differentiator here is managing those integrations like a real software company and thus cutting costs?