We did consulting. We did custom, turn-key, machine learning products exclusively for large enterprise for many years. That wasn't just building the models, but everything from digging into ISO standards for rail transportation, to data acquisition, infra, building models, writing applications, and sometimes having custom hardware made for very specific signals of interest. Tiny team. Repeat business as our clients rely on us more and more with a history of delivering.<p>We're builing our machine learning platform[0] to remove as many problems we had faced as possible and execute projects in a faster, more reliable, and more consistent way.<p>I had a big grin a few weeks ago when a client was describing what was to be done, and I DM'd our CEO saying that this was about three months of work we wouldn't be doing, <i>after</i> it had saved us about two weeks of work up until that point.<p>To recap: we did consulting, learned a lot while being profitable, then leveraged what we learned and all the problems we had and the mistakes we made to build our machine learning platform to get data projects right.<p>I wrote a bit about this in a twitter thread[1]. Feel free if you have questions, as I think we're in similar situations for similar clients.<p>Thread reproduced here for convenience. Context: Projects are in the mid six-figure range, a couple of individuals can pull the project off. Clients are large corporations. Domain is machine learning (turn-key, taking clients from puzzled look to wide smile).<p>===<p>0. Form:<p>0.0. It pays to provide services through a company. Companies write large checks to companies without blinking; not so large for individuals.<p>1. Contracts:<p>1.0. Get a lawyer to prepare contracts for collaborations. Someone at some point might disagree or have trouble remembering what they have agreed to pay you, make sure to have a mnemonic device in the form of a clear contract.<p>1.1. Companies have typical contracts for collaboration: don't sign anything without legal counsel.<p>1.2. Retain intellectual property to amortize engineering and sell what you make to others.<p>1.3. Companies might ask that you do not sell to competitors: define them and contain geographic zone and duration. Get paid for the opportunity cost.<p>1.4. Split project into tranches for which you get paid. This can help cash-flow and reduce risk, especially in the beginning.<p>2. Presentation:<p>2.0. Your company solves problems and being open minded about these problems is useful; so it's not much about finding problems for your solutions, but more like finding solutions to clients' problems.<p>2.0.0 After enough problems you built solutions for, patterns emerge and you can abstract a solution that serves several use cases. See "Abstraction" section.<p>2.1. General presentation with broad strokes of your capabilities, including previous work with other clients<p>2.2. Conversation with the prospect on their worries in a given space<p>2.3. Conversation with the prospect on their worries in a given space<p>2.4. Extract problems from that conversation and send a list of N problems to solve/ideas to explore.<p>2.5. The client finds one problem urgent/highest priority/highest value<p>2.6. You get together and talk about "desirability, fasiblity, viability".<p>2.7. Once you agree on what to do, prove the concept.<p>2.7.0. e.g: organizations give us data and ask us to predict something, say customer churn or subway car malfunction. We return predictions, they validate the predictions, and we can then start the project because they have proof we actually can predict what they want us to.<p>3. Execution:<p>3.0. Your opinion on what is valuable for the client does not matter. It doesn't have to be valuable to you, only to the client. A client who gets excited by a functionality that took one hour to implement because it solves a real problem is a learning experience.<p>3.1. Go above and beyond. Some sectors/clients are hard to get in, but once you're in, you're in.<p>3.2. Listening and assuming the client is smart goes a long, long, long way.<p>3.3. Send meeting notes to the client. It clears ambiguities during/after the project.<p>3.4. Press to get the client's domain experts' collaboration. They will actually use what you're building. Get them at the table.<p>3.5. Some of the most valuable insights are gleaned after a meeting and not necessarily with your "counterpart".<p>Don't build the wrong thing.<p>4. Abstract:<p>4.0. When you solve many problems, some patterns emerge. You built custom products for your clients, but you can abstract functionality and build tooling to scale your services, and enable others to do the same.<p>4.0.0. e.g: we we built machine learning products for enterprise clients. After many projects, we built iko.ai, our own machine learning platform to "Get Data Products Released".<p>4.1. One advantage of this approach is to explore the space while being profitable. Some problems exist not for lack of a nice front-end or lack of knowledge of the target audience. Coming at them from a purely "webdev"/"devops" mindset can bring bad surprises.<p>All the best,
===<p>- [0]: <a href="https://iko.ai" rel="nofollow">https://iko.ai</a><p>- [1]: <a href="https://twitter.com/jugurthahadjar/status/1310668293305499653" rel="nofollow">https://twitter.com/jugurthahadjar/status/131066829330549965...</a>