KnubiSoft makes the boring parts work.

A laundry bag is a surprisingly good place to start a story about software. At PYCK, the laundry-service business in KnubiSoft’s portfolio, a QR code connects the physical bag to its digital progress. Someone places an order. Someone else handles the clothes. Both need to know what happens next. The app has to keep up with the washing.

KnubiSoft built an Android and iOS application, a back-office portal, and the connections to payments and invoicing. There is a useful lesson in that unglamorous assignment. A button on a phone is only the visible tip of an operation. The interesting engineering happens underneath, where a customer’s expectation meets somebody else’s working day.

A bag of clothes, a file of evidence

KnubiSoft occupies the space between an idea and a functioning business system. Its services include discovery, interface design, minimum viable products, application development, quality assurance, and ongoing support. A client can commission a project or bring KnubiSoft specialists into an existing team. The company sells both the finished work and the capacity to get work done.

The contrast between two assignments makes its range concrete. PYCK needs order status, pickup details, QR scanning, and a way for staff to manage the service. For Octopus, KnubiSoft describes building a document-management application around MiFID II requirements. That project involves collecting records, controlling versions, comparing documents, and tracking changes. The portfolio lists 1,920 hours and an eight-person team.

Laundry and investment paperwork share a less obvious problem: information must stay attached to the thing it describes. Lose that connection and people start asking questions the system should already answer. Where is the order? Which document is current? Who changed it? KnubiSoft’s more persuasive pitch lives in those questions.

Seven years to a testing product

Then there is the software KnubiSoft developed for testing software. Testlum’s published chronology starts with an idea in 2016, records a first version in 2019, and places launch in 2023. Seven years separate the first and last milestones. That is a useful detail for anyone tempted to assume that an internal capability becomes a sellable product over a long weekend.

The product addresses an awkward dependency. A team may understand exactly how an application ought to behave while lacking the programming expertise to automate those checks. Testlum offers a visual builder and recorder, with scenarios stored in XML. Its scope includes websites, mobile applications, APIs, and databases. The aim is to let testers describe a journey across those boundaries.

Its public GitHub example is refreshingly specific: click a sign-in button, check users in a database, then request a profile through an HTTP endpoint. The engine is published under Apache 2.0. A separate demo repository supplies sample configuration and runnable tests. Buyers can inspect a real example before deciding whether the approach fits their own application.

“We found KnubiSoft’s approach consultative rather than 'salesy'”

Steve Grice · COO, Trustap

The arithmetic behind the demo

This makes KnubiSoft a hybrid of services provider and product builder. The distinction matters when buying. A development engagement pays for people, coordination, and delivery. A testing subscription pays for a tool. KnubiSoft’s Clutch listing advertises hourly rates of $25-$49 and a minimum project size of $25,000. Those figures are a starting point for a conversation about scope.

Testlum’s pricing page lists Pro at $49 per user per month. Its Enterprise offering adds options such as private deployment, custom integrations, onboarding, and team augmentation. The practical question is how much work remains around the subscription: preparing data, defining expected results, connecting environments, and maintaining scenarios as the application changes.

A sensible evaluation would use one important business journey. Measure the effort to build it, run it, diagnose a failure, and update it after a change. A tool that saves execution time but makes failures harder to understand can move the bottleneck. A visual editor still needs someone who knows what should happen.

Reliability needs electricity

In 2022, KnubiSoft faced a delivery problem no testing framework could solve. Contemporary reporting describes business operations stopping during the first week of Russia’s full-scale invasion of Ukraine. The company had a continuity plan but could not fully implement it. As danger intensified and internet connections deteriorated, management concluded that evacuation was necessary. Employees relocated within Ukraine and abroad.

By February 2023, AIN reported offices in Kyiv, Lviv, and Kharkiv equipped with generators and Starlink. The arrangements included room for an employee to bring one relative during a full blackout. That small provision says something concrete about running a business: a reliable workstation is less useful if the person using it is worried about someone at home.

The careers page adds another side of the operating model: professional education support, English classes, a training center, and hybrid work. Its Education Center advertises online Java, QA, and lead-generation courses lasting three to four months. For a company selling engineering capacity, teaching people is directly connected to what it can deliver.

Start with the question that keeps coming back

KnubiSoft’s place in the market becomes clearer when the work needs both a custom workflow and people to build it. For a standard task already handled by packaged software, bespoke development needs a stronger justification. For a team with mature automation, replacing existing tests also needs to earn its keep. Fit depends on the work already in place.

The most portable idea here is to follow one troublesome handoff. Give it an identity. Make its status visible. Test what happens on both sides. A laundry bag and a compliance file make the same demand: keep the information with the work.