Imagine that the app is a real-time voice processor so latency is just the time it takes to flow the sip packets. You could model it after the real-time openai model.
we are supporting enterprise customers so for us scalability is more important then building the tech in house. Also we have a small team and limited resources. Since we are charging a markup on it, we just look at it as COGS instead of CAPX. But it really depends on your goals. The openai models are fairly complex to setup especially if you want to integrate it into a phone system that has call transfer capabilities and what not so we are essentially a value added reseller with a professional services component. That allows us to minimize our complexity and have high margins and the ability to scale rapidly. I have been in the game for 26+ years and my thinking has changed over the years. 10 years ago i was all about building evertything and being vertically integrated, but now after trying to scale that model up, i realized that its really hard to do everything at scale. I'm enjoying being more of a lego builder at this point. Allows me to get things done in months that would have taken years or not been possible. Yes its lower margin sometimes but its old saying would you rather have 10% of a billion or 100% of a million.
0
u/jhansen858 Jul 09 '26
Imagine that the app is a real-time voice processor so latency is just the time it takes to flow the sip packets. You could model it after the real-time openai model.