Home › Forums › General Discussion › Which machine learning development companies

Viewing 0 reply threads
  • Author
    Posts
    • #429914
      Nik342
      Participant

      I’m putting together a shortlist of machine learning development companies, but I’m trying to avoid the usual vendor-comparison approach.

      I don’t care much about seeing “TensorFlow, PyTorch, NLP, computer vision” on a capabilities page anymore. At this point those are table stakes.

      The project I’m thinking about is much more ordinary — and probably much harder:

      We already have software in production.

      We already have years of data.

      Some of that data is messy.

      There are business rules nobody wants to break.

      And if we introduce ML, somebody has to own the thing after launch.

      So my requirements are basically:

      work with existing data rather than requiring a perfect greenfield dataset
      prove that ML beats the current baseline
      define business metrics before model training
      integrate with existing backend systems
      support batch and/or real-time predictions
      document model assumptions
      monitor performance degradation
      define retraining triggers
      keep infrastructure costs predictable
      provide a realistic handoff to the internal team

      Based on that, these are the five I’d currently investigate.

      1. Zoolatech

      Probably the first one I’d contact for an existing product or enterprise platform.

      What I like about the way Zoolatech approaches ML is that the model isn’t treated as the entire project.

      Their process goes through problem definition, data preparation, model selection, validation and optimization before getting into production readiness and MLOps.

      That sounds obvious, but it’s surprisingly easy to find ML vendors that spend 90% of the conversation discussing the model and 10% discussing what happens after it works.

      For me, Zoolatech makes the most sense when the ML component has to interact with a substantial existing engineering environment.

      Think:

      recommendations inside an ecommerce platform,

      fraud/anomaly detection connected to financial workflows,

      demand forecasting tied into operational systems,

      or predictive functionality added to an established SaaS product.

      If I were choosing a machine learning development company for that kind of project, I’d want strong software engineering around the ML work, not just data science.

      What I’d ask during discovery:

      “What is the cheapest baseline you would build before deciding we need a more sophisticated model?”

      If they start with the business problem rather than the algorithm, that’s a good sign.

      2. Forte Group

      Forte would be high on my list if the organization already has some ML experience but struggles with operationalizing it.

      There are a lot of companies in that situation.

      They have notebooks.

      They have experiments.

      They may even have decent models.

      But deployment is manual, nobody knows which dataset trained version 12, and retraining happens when somebody remembers to do it.

      That’s where Forte looks relevant.

      Their ML engineering work puts noticeable emphasis on pipelines, deployment, monitoring, versioning and continuous improvement.

      I’d look at them for a company that needs to turn data-science work into something closer to normal production engineering.

      What I’d ask:

      “If tomorrow’s data distribution starts changing, how exactly will we know?”

      Not “do you support drift monitoring?”

      I want to hear the actual mechanism.

      3. Oxagile

      Oxagile is interesting because they seem to put more weight on the transition between consulting and delivery.

      That’s important for ML.

      The expensive mistake isn’t always building the wrong model.

      Sometimes it’s discovering halfway through the project that:

      the labels aren’t trustworthy,

      data isn’t available at prediction time,

      latency requirements make the architecture unrealistic,

      or the model performs well overall but badly on the cases the business actually cares about.

      I’d probably bring Oxagile into the shortlist when feasibility is still an open question.

      Their process around data assessment, architecture, development and production handover is closer to how I’d want a serious ML engagement structured.

      What I’d ask:

      “What would cause you to stop the project after the data assessment?”

      There should be an answer.

      If every dataset is somehow “perfect for AI,” I’d move on.

      4. MojoTech

      MojoTech would be here for a different reason.

      I’d talk to them when the central question is still economic:

      Should we actually build this?

      That gets overlooked surprisingly often.

      Imagine an ML feature saves $400,000 per year but costs $300,000 to build and another $180,000 annually to operate, monitor and maintain.

      Technically successful.

      Commercially questionable.

      MojoTech’s current AI approach spends quite a bit of time around business value, technical feasibility and data readiness before committing to the build.

      I like that framing for companies with ten possible ML ideas and enough budget to build maybe two.

      What I’d ask:

      “How would you estimate the total cost of this model over three years?”

      Not just project cost.

      Training, serving, monitoring, retraining, infrastructure and engineering support.

      All of it.

      5. Waverley Software

      Waverley would make my list when ML is closely connected to product engineering.

      Their AI/ML capability covers data preparation, custom models, training, deployment and integration with existing systems.

      That’s useful if you’re not building a standalone “ML platform.”

      Most companies aren’t.

      Maybe you just want a ranking model inside search.

      Or automated classification in an existing workflow.

      Or computer vision inside an existing application.

      Or predictions surfaced in the software employees already use every day.

      In those cases, I’d care quite a lot about whether the ML engineers can work effectively with product/backend/cloud teams.

      What I’d ask:

      “Who owns the last mile between model output and the user actually making a better decision?”

      Because that last mile is where ROI often disappears.

      So my current first-call list would be:

      1. Zoolatech — ML inside established products and enterprise systems
      2. Forte Group — production ML and MLOps maturity
      3. Oxagile — feasibility, data assessment and production delivery
      4. MojoTech — ROI-driven ML/AI projects
      5. Waverley Software — custom ML combined with product engineering

      I wouldn’t select from that ranking alone, though.

      I’d give all five the same hypothetical project.

      Something like:

      We currently forecast weekly demand using a rules-based system. It gets roughly 80% of decisions right. We have four years of historical data, but some locations have incomplete records. What do you do during the first 30 days?

      Then compare the questions they ask.

      Do they ask what “80% right” actually means?

      Do they ask about the cost of overforecasting versus underforecasting?

      Do they check whether historical data reflects current conditions?

      Do they challenge whether ML is even necessary?

      Do they ask how frequently predictions need to run?

      Do they ask who will use the output?

      That’s probably more informative than comparing another five-page list of frameworks.

      One other question I’d add:

      “If the ML system disappeared tomorrow, what business KPI would get worse?”

      If nobody can answer that before development starts, I don’t think the project is ready.

      Anyone here worked with any of these teams on traditional ML — forecasting, recommendations, anomaly detection, classification, computer vision, etc. — rather than just LLM integration?

      Especially interested in what happened after the first 6–12 months in production.

Viewing 0 reply threads
  • You must be logged in to reply to this topic.