![]() Some problems exist not for lack of a nice front-end or lack of knowledge of the target audience. One advantage of this approach is to explore the space while being profitable. After many projects, we built iko.ai, our own machine learning platform to "Get Data Products Released".Ĥ.1. e.g: we we built machine learning products for enterprise clients. 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.Ĥ.0.0. When you solve many problems, some patterns emerge. Some of the most valuable insights are gleaned after a meeting and not necessarily with your "counterpart".Ĥ.0. They will actually use what you're building. Press to get the client's domain experts' collaboration. It clears ambiguities during/after the project.ģ.4. Listening and assuming the client is smart goes a long, long, long way.ģ.3. Some sectors/clients are hard to get in, but once you're in, you're in.ģ.2. A client who gets excited by a functionality that took one hour to implement because it solves a real problem is a learning experience.ģ.1. It doesn't have to be valuable to you, only to the client. Your opinion on what is valuable for the client does not matter. 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.ģ.0. e.g: organizations give us data and ask us to predict something, say customer churn or subway car malfunction. Once you agree on what to do, prove the concept.Ģ.7.0. You get together and talk about "desirability, fasiblity, viability".Ģ.7. The client finds one problem urgent/highest priority/highest valueĢ.6. Extract problems from that conversation and send a list of N problems to solve/ideas to explore.Ģ.5. Conversation with the prospect on their worries in a given spaceĢ.4. Conversation with the prospect on their worries in a given spaceĢ.3. General presentation with broad strokes of your capabilities, including previous work with other clientsĢ.2. 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.Ģ.0.0 After enough problems you built solutions for, patterns emerge and you can abstract a solution that serves several use cases. This can help cash-flow and reduce risk, especially in the beginning.Ģ.0. Split project into tranches for which you get paid. Companies might ask that you do not sell to competitors: define them and contain geographic zone and duration. ![]() ![]() Retain intellectual property to amortize engineering and sell what you make to others.ġ.3. Companies have typical contracts for collaboration: don't sign anything without legal counsel.ġ.2. ![]() 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.ġ.1. Get a lawyer to prepare contracts for collaborations. Companies write large checks to companies without blinking not so large for individuals.ġ.0. It pays to provide services through a company. The context is enterprise products in the mid six figures that a couple of individuals can pull off.Ġ.0. It deals with the fact you'll get paid way more if you're a company than an individual, product development, protecting yourself, foot in the door, and then expanding and abstracting. I wrote a twitter thread you might find useful, especially as a relatively new freelancer. We generate a PDF, send the invoice, then we get paid.Ĭaveat emptor: we've been building custom machine learning products exclusively for large enterprise for seven years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |