Background & Opportunity
TFY’s development can be understood as a sequence of increasingly valuable customer problems. The company was founded by Lilia Stoyanov in London in 2015. In 2016, its MVP was a free Applicant Tracking System for remote jobs and a related job board. This was a logical starting point for a company focused on remote work: employers needed help discovering candidates, and candidates needed access to relevant opportunities. The product could attract participants without asking them to commit to a paid system at the beginning. That model, however, placed TFY near the beginning of the employment process. A company might use the platform to identify a remote worker and then complete the rest of the relationship elsewhere. Early revenue came mainly from partners and affiliate programs, while direct SaaS subscription revenue had not yet formed. The product generated reach, but it did not necessarily control the administrative work that followed a hiring decision. The difference between attracting a user and becoming operationally important became the central strategic issue. Remote hiring creates a chain of activities rather than a single event. Once a business selects an international contractor, it must manage the relationship, record the arrangement, handle relevant compliance, receive or generate invoices, make payments and reconcile the resulting information. When those activities are divided among multiple tools and providers, the employer bears coordination costs. The recruitment platform may have helped find the person, but it may not have remained involved in the most frequent or sensitive parts of the relationship. TFY’s opportunity was to move along that chain. In 2018, TFY piloted a Freelancer Management System. This was an important product extension because it brought existing contractors into the platform instead of limiting the relationship to candidate discovery. The company could observe how customers managed freelancers and where the workflow remained difficult. The verified founder interview describes commercialization beginning in 2020, after customer workflows had formed. The sequence suggests a deliberate approach: acquire and learn through a free entry product, develop a management layer around repeated customer behavior, and charge when the service addresses a material operating requirement. The commercial question was not merely whether TFY could add payment. Payment alone is a crowded and demanding category. A standalone payment application must compete on trust, infrastructure, cost, speed, geographic reach and regulatory capability. Banks and large financial technology companies already operate at scale in those areas. TFY instead positioned payment as one feature in a broader work-management system. That framing connected the transaction to a business process the company understood: recruiting and managing global contractors. AOR became the key expression of that strategy. The verified materials describe TFY as enabling an enterprise to use one partner for international contractor onboarding, contracts, compliance, invoicing and payment. The value proposition was therefore not “send money to a worker.” It was “manage the relationship from engagement to payment through a coordinated operating layer.” This distinction gave the company a more complete answer to the customer’s problem. It also meant that the customer’s data, tasks and operational habits could be concentrated in a single platform, potentially making substitution more difficult. The decision had implications for monetization. The original free ATS and job board could generate attention and partner-related revenue, but enterprise customers had stronger reasons to pay when the platform handled recurring administrative and financial activities. TFY’s business model combined B2B SaaS with transaction services. Enterprise subscriptions and platform fees could support software capabilities, while contractor-payment-related services connected revenue to activity on the platform. The company did not need to choose between software and payments; it could make their combination meaningful by placing both inside one workflow. This integration also changed the nature of the customer relationship. A job board is often evaluated by reach and candidate supply. A contractor-management platform is evaluated by reliability, compliance, process control and ease of administration. A payment service is evaluated by successful and timely execution. Combining these expectations increases the standard TFY must meet, but it also increases the potential value of success. A customer that uses recruitment, contractor records, invoicing and payments together may have more reasons to renew than a customer that only posts or searches for jobs. TFY’s current positioning reflects that expansion. Its website describes AI ATS, AOR or Contractor of Record services, global contractor payments and an integrated platform for hiring, managing and paying global talent in more than 184 countries. The country figure is a company-reported coverage claim, and the research does not independently establish identical local capabilities in every country. Still, the positioning demonstrates the scale of the intended problem. TFY is no longer presenting itself mainly as a source of remote job listings. It presents a connected infrastructure for global workforce operations. Publicly reported performance gives the strategic shift commercial significance. The founder interview states that revenue in 2021 grew 600% compared with 2020 and that revenue in 2022 grew 250% compared with 2021. A 2023 interview says revenue doubled, churn was below 1%, and approximately 80% of customers came through referrals. TFY’s 2025 company article says that 2024 profit grew 90%, connecting the result with AI recruitment tools, the contractor-management platform, Open API integration, and adoption in the United Kingdom, United States and Europe. These figures should be used carefully. They are mainly company or founder self-reported claims. The research did not verify them through formal UK financial statements, and the absolute revenue and profit amounts were not disclosed. “Revenue growth” could reflect customer acquisition, pricing, product mix, transaction volume, or accounting scope. “Churn below 1%” requires a defined time period and denominator. “Approximately 80% through referrals” requires clarity about whether it covers all customers, new customers, or a selected period. The claims are useful evidence of the company’s reported trajectory, but not substitutes for independently audited performance. The strategic mechanism remains clear even with those limitations. TFY identified a gap between talent discovery and talent administration. It expanded into Freelancer Management, then used AOR to connect the activities that became burdensome after hiring. It treated payment as part of the customer’s operating workflow, not as an isolated application. That made the product more relevant to enterprise operations and created additional places where the company could charge. The move also gave free acquisition a potential path toward paid adoption: customers could enter through recruitment and expand when they needed administration and payment. The strategy’s defensibility depends on execution. An integrated global workforce service must manage product quality, customer support, payment operations, compliance requirements and local market differences. A problem in one area could affect confidence in the whole relationship. A platform that promises broad country coverage must demonstrate what that coverage means in practice. The evidence notes that local compliance capability, payment margins, customer concentration, actual conversion, referral definitions and switching costs require further examination. These are especially important because the business combines software with services whose cost and risk may vary by location and transaction. TFY’s choice also shows why product sequencing matters for a bootstrap company. A free product can lower acquisition friction and create a community or user base. But free access alone does not establish sustainable economics. The company needed to identify the point at which customers received enough operational value to pay. By extending from ATS to FMS and then to AOR, TFY followed the customer’s process instead of attaching an unrelated paid product to the original free tool. This continuity strengthened the logic of the commercial transition. The case is therefore not a claim that every recruitment platform should add payment. The lesson is more specific: when the customer’s real problem extends beyond the first product interaction, the company should investigate whether it can own the next critical workflow. For TFY, the next workflow included contractor management, compliance, invoicing and payment. AOR linked those tasks and gave the company a more defensible position than remote job discovery alone. It also provided a practical answer to the risk of becoming a standalone fintech competitor. The result, according to public interviews and company materials, was a profitable and growing business with reported low churn and referral-led acquisition. The strongest conclusion is not that every reported metric has been independently proven. It is that the product and business-model transition created a coherent explanation for the company’s reported progress. TFY moved toward a higher-value relationship by helping enterprises manage what happened after they found global talent. The platform’s economic promise came from connected workflow, not from any single feature. For leaders considering a similar move, the decision should be tested through adoption and economics. Measure how many customers use multiple modules, whether recruitment users adopt contractor management, whether payment activity persists, and whether the contribution after compliance and service costs is attractive. Define churn and referral metrics precisely. Examine country-level operating requirements rather than relying only on a headline coverage number. Validate whether the product creates real switching costs or merely bundles services that customers can replace independently. These tests would turn TFY’s strategic narrative into a repeatable management framework. TFY’s story ultimately describes a shift from reach to responsibility. The free ATS and job board helped the company reach remote-work participants. The FMS and AOR model accepted responsibility for more of the employer’s ongoing process. Compliance, invoices and payments made the relationship operationally important, while AI ATS and integrations extended the recruitment side. That combination supported the reported movement from partner and affiliate revenue toward enterprise subscriptions, platform fees and transaction services. The transformation’s central insight was simple but consequential: payment becomes more defensible when it is embedded in the work that creates the payment.
Original Problem / Model
TFY’s early product solved talent discovery, not the full employment workflow. A free remote-job ATS and job board could attract employers and candidates, but customers still had to manage international contractors, contracts, compliance, invoices, payments and reconciliation elsewhere. This fragmented process created coordination costs and limited TFY’s role after a hiring decision. Early monetization through partners and affiliate programs also did not establish direct SaaS subscription revenue. By observing recurring post-hire needs, TFY could extend into Freelancer Management and later AOR. That expansion made the platform more operationally important, created more frequent reasons for customers to return, and provided a clearer basis for enterprise subscriptions, platform fees and transaction services. The opportunity was not simply to add a payment button. It was to connect recruitment with the administrative work that followed, while keeping payment within a broader workflow rather than competing as an isolated financial application. The evidence supports this product sequence, but does not independently quantify conversion rates, switching costs, payment margins or the proportion of early users who became paying enterprise customers.
Turning Point
The key design choice was to avoid becoming only a payment application. Payment was positioned as one step in a broader process that included recruitment, onboarding, contracts, compliance, invoicing and contractor management. This gave TFY a workflow-based value proposition and linked transaction services to software usage. It also reduced dependence on competing solely with banks and large fintech providers on payment infrastructure, price or scale. AOR made one partner responsible for coordinating the international contractor relationship, potentially increasing convenience and customer reliance. The evidence does not establish identical capabilities in every stated country, nor does it quantify switching costs or margins, so those advantages remain hypotheses requiring operational and financial measurement.
Core Decision
AOR connected the customer’s fragmented tasks through one partner. That integration could increase convenience and potential switching costs, while giving TFY more opportunities to monetize subscriptions, platform fees and payment-related services. The evidence does not quantify switching costs or margins, so both remain hypotheses requiring measurement.
Execution / Model / Acquisition Changes
The transition followed a staged sequence. TFY began with a free ATS and job board in 2016, added a Freelancer Management System in 2018, and commercialized in 2020 after customer workflows had formed. AOR then became the central bridge between finding talent and managing the resulting contractor relationship. The platform combined onboarding, contracts, compliance, invoicing and payment, while later positioning included AI ATS, Open API integration and global coverage. This sequence mattered because it allowed commercialization to follow observed customer activity. The company did not simply place a price on the original free product or launch an unrelated payment service. It expanded around a problem customers encountered repeatedly after hiring. That created a clearer reason to pay and a more continuous product narrative from acquisition to enterprise operations.
Measurable Results
Public materials report significant performance after the transition. The founder interview says revenue grew 600% in 2021 versus 2020 and 250% in 2022 versus 2021. A 2023 interview reported doubled revenue, churn below 1% and approximately 80% of customers acquired through referrals. TFY later stated that 2024 profit increased 90%. These figures are important signals, but they are not independently verified audited results in this research. Their definitions and drivers remain open questions. Growth may reflect customers, pricing, transactions, product mix or accounting scope. Churn needs a period and denominator, while referrals need a precise population. The figures support the reported direction, not an independently proven financial conclusion.
Lessons
The transferable lesson is to follow the customer’s workflow beyond the initial product entry point. TFY moved from helping companies find remote talent to helping them manage global contractors after hiring. AOR made compliance, invoicing and payment part of that relationship, creating a broader SaaS and transaction-services model and a path from free acquisition to paid enterprise use. The strategy should still be tested through module adoption, payment persistence, contribution margins after compliance and service costs, country-level capability, customer concentration, precise churn definitions and actual switching costs. Reported growth, profit and referral figures are useful signals, but they are company or founder self-reported rather than independently verified audited results. The broader lesson is therefore conditional: integrated workflow can create more value than a single feature only when execution, economics and local operating requirements support the promise.