Starpoint Solutions sold the team. And the work.

A visitor looking for Starpoint Solutions encounters an unusually practical piece of corporate archaeology. Yoh’s handoff page offers two destinations. Need software engineering? Go to Softlab360. Looking for financial technology staffing? Go to Yoh. A company that once put both services under one name now explains itself with a choice.

• The offer: recruit specialists or commission a technology project.
• The turning point: Yoh acquired Starpoint in October 2016.
• The afterlife: the brand is inactive; staffing and engineering have separate destinations.

That little fork in the road is also the best introduction to the business. Technology buyers can describe the same predicament in very different ways. “We need a developer” assigns the problem to a vacancy. “We need this system working” assigns it to a result. Starpoint made room for both descriptions.

A vacancy is only one diagnosis

Established in 1982, Starpoint grew into a New York consultancy with two practices: Staffing Solutions and Project Solutions. The first found professionals. The second organized expertise into delivered work. Its historical offering included custom applications, enterprise resource planning, cloud systems and analytics. Recruiting and engineering occupied the same commercial address.

Consider the difference from a buyer’s chair. A capable internal technology department may need one specialist for a difficult stretch. Another organization may need a vendor to assemble the team, manage the project and integrate the result. Those are different allocations of responsibility, even when the engineers use identical tools.

Starpoint’s 2013 corporate presentation made that flexibility explicit. It described outsourced teams, project augmentation and combinations of work at client and company sites. It also claimed a 75% repeat business rate. Treat that as a historical company claim, but notice what the firm chose to advertise: customers coming back.

The interesting work happens backstage

The company’s customers were organizations with systems to maintain, calculations to perform and people depending on the answers. Contemporary reporting on the 2016 acquisition named SEI, Siemens/Cerner, Towers Perrin, Fidelity Investments and Bank of Tokyo among past clients. Enterprise implementations could involve SAP, PeopleSoft or Oracle rather than a new application invented from scratch.

SEI supplies a particularly useful example. The engineering history now published by Softlab360 describes a tax-lot calculation preprocessor: a way to handle complicated investment calculations more efficiently. The team moved from a pilot to production and integration with the customer’s systems. This is software whose importance becomes clearer when you imagine an incorrect answer.

Payments offer another view. The same engineering lineage supported BlueSnap from 2015, working on architecture and integrations. Softlab360 describes becoming its first authorized integration and implementation partner. The object was to connect payment capabilities to other businesses and systems. The work lived between products, where a sales brochure’s clean boundaries become somebody else’s technical problem.

These examples explain Starpoint’s place in the market. It sold professional expertise and implementation capacity. A buyer was purchasing people, engineering work or project execution. The attraction lay in accommodating an existing business, with its inherited systems and operating rules. That is a different purchase from subscribing to a ready-made software product.

What Yoh wanted to buy

Yoh’s acquisition closed on October 14, 2016. The announcement emphasized a move toward project-based talent services, specifically application development, ERP implementation and analytics. The buyer wanted a broader answer to a client’s technology needs. Financial terms were undisclosed.

“Strictly transactional staffing relationships are no longer the only answer”Anthony Bosco, Yoh President, October 2016

The Philadelphia Inquirer reported approximately 850 workers and $100 million in annual sales at Starpoint around the transaction. Those numbers describe the business then. The same report put the combined companies above $700 million in annual sales, with about 8,000 workers. For Starpoint, the deal meant joining a much larger workforce organization.

Founder Jeffrey Najarian’s financing history adds another turn. A later SEC biography says Goldman Sachs took a minority stake through its venture fund; Najarian subsequently bought it back and recapitalized the firm. Outside capital, repurchased ownership and an eventual strategic sale all appear in the record. They should not be mistaken for a conventional sequence of venture rounds.

The name retires. The distinction survives.

The engineering branch has its own chronology. Softlab360 says Henry Zelikovsky founded that business in 2000, merged it with Starpoint in 2002 and led it as Starpoint’s software engineering division until it became independent in 2021. He became Softlab360’s CEO in July of that year.

Starpoint’s LinkedIn page now says its brand is no longer active. The public routing agrees: Yoh for staffing, Softlab360 for engineering. Keeping that distinction matters when reading case histories. A project described by the successor today does not automatically establish a new accomplishment by Starpoint.

There is continuity in the subject matter, however. Softlab360’s August 2026 commentary discusses wealth-management technology and contextual AI. Earlier engineering concerns about integrations and usable data remain recognizable. The tools and names have changed; financial businesses still need their systems to communicate.

Buy the responsibility you need

The portable lesson is a procurement decision. Before seeking candidates or collecting project proposals, decide what your organization can manage. If it can direct the work and judge the implementation, additional specialists may be enough. If it needs a delivery partner, define the scope, acceptance criteria and responsibility for integration before treating a list of skills as a solution.

That approach depends on a buyer who can explain the operating problem. A vague brief will remain vague after more engineers arrive. A small, standard requirement may also be better served by existing software than a custom engagement. Starpoint’s history makes the choice visible: decide whether you are buying capacity or execution, then write the agreement accordingly.