Three months of Tapix: what we shipped and what's next | Tapix [ ![Tapix](/img/tapix-logo-light.svg) ![Tapix](/img/tapix-logo-dark.svg) ](https://tapix.dev) [Features](https://tapix.dev#features) [Pricing](https://tapix.dev#pricing) [Docs](https://docs.tapix.dev) [Blog](https://tapix.dev/blog) Try Demo [ Get Tapix from $99](https://tapix.dev#pricing) [Features](https://tapix.dev#features) [Pricing](https://tapix.dev#pricing) [Docs](https://docs.tapix.dev) [Blog](https://tapix.dev/blog) Try Demo [ Get Tapix from $99](https://tapix.dev#pricing) ![Tapix](https://tapix.dev/img/tapix-logo-light.svg) ProductThree months of Tapix: what we shipped and what's next ====================================================== tapix.dev/blog [ Back to blog ](https://tapix.dev/blog) [ Product ](https://tapix.dev/blog/category/product) Three months of Tapix: what we shipped and what's next ====================================================== Manch Minasyan · July 14, 2026 · 6 min read The bet was that writing deeply technical content about CSV imports before shipping a single line of installable code would build a customer base. Three months later, early access customers have come almost entirely through organic search. Here is what happened. [\#](#why-we-started-writing "Permalink")Why we started writing --------------------------------------------------------------- Most Laravel packages launch with a README, a few code examples, and a hope that word spreads. We took a different approach. Before Tapix ships a single line of installable code, we wanted to own the conversation around CSV imports in Laravel -- not with marketing spin, but with genuinely useful technical content. The reasoning was simple. Every Laravel developer who has built an import feature has run into the same problems: messy column mapping, validation nightmares, relationship resolution, queue orchestration, multi-tenancy scoping. These problems are well-understood individually but poorly documented as a cohesive domain. Nobody had written the definitive resource for handling them together. So we did. We started with [The complete guide to CSV imports in Laravel](/blog/complete-guide-csv-imports-laravel) as the anchor piece and expanded from there, one topic per week, covering the full surface area of what makes CSV importing hard. [\#](#twenty-seven-posts-in-three-months "Permalink")Twenty-seven posts in three months --------------------------------------------------------------------------------------- Since launch, we have published 27 posts across four categories: tutorials, best practices, architecture deep dives, and product updates. The range was intentional. Some posts are beginner-friendly walkthroughs. Others are opinionated takes on patterns we have seen break in production. A few are detailed architecture explorations that pull back the curtain on how Tapix works internally. Here is what we covered: **The foundations.** How to handle CSV validation errors in Laravel. Importing relational data without losing your mind. Queue-powered imports that scale to 100,000+ rows. These are the posts that address the core problems every importer faces. **The details that matter.** Auto-detecting column types from raw CSV data. Parsing numbers and currency values across locales. Detecting date formats without configuration. Handling boolean and choice fields gracefully. These are the problems that seem small until they corrupt your data. **The patterns.** Match-or-create logic for relational imports. Intra-import deduplication. Import lifecycle hooks for custom behavior. Error recovery strategies that let users fix and retry without re-uploading. These are the architectural decisions that separate a toy importer from a production system. **The comparisons.** [Laravel Excel vs. Tapix](/blog/laravel-excel-vs-tapix) -- different tools for different jobs. [When Filament's built-in Import Action is enough](/blog/filament-import-action-when-enough) and when it is not. [Self-hosted imports vs. hosted SaaS platforms](/blog/csvbox-vs-self-hosted-import) like CSVBox. Honest assessments, not sales pitches. **The architecture.** Column mapping UX patterns. The hidden cost of building your own importer. Tapix under the hood. How we built the Filament integration. These posts explain not just what to do, but why we made the choices we did. ### [\#](#what-performed-best "Permalink")What performed best The [complete guide to CSV imports in Laravel](/blog/complete-guide-csv-imports-laravel) remains the top performer by a wide margin -- it ranks for dozens of long-tail search terms and consistently drives the most traffic and conversions. The [Laravel Excel vs Tapix](/blog/laravel-excel-vs-tapix) comparison post and the [Filament Import Action limitations post](/blog/filament-import-action-when-enough) also performed well, pulling in readers who were actively evaluating their options. On the tutorial side, the [queue-powered imports post](/blog/queue-powered-imports-100k-rows) and the [column mapping UX post](/blog/csv-column-mapping-ux-patterns) resonated with developers in the middle of building their own solutions. Organic search has been the primary traffic driver, with readers already looking for answers on how to handle CSV imports in Laravel. [\#](#community-response "Permalink")Community response ------------------------------------------------------- We are not publishing traffic numbers, but the conversion path is what we expected: readers land on a technical post, explore related articles, and a meaningful percentage click through to the pricing section. Early access customers have come almost entirely through blog content rather than direct marketing. Each new post adds permanent search surface area, and older posts continue to climb as the domain builds authority. The questions we receive have shifted. Early on, people asked "what is Tapix?" Now they ask "when does it ship?" and "will it support X?" That shift from awareness to intent is the signal the content strategy is working. [\#](#what-is-next "Permalink")What is next ------------------------------------------- Three months of writing about the problem. Now it is time to ship the solution. Here is what we are working toward: **Documentation site.** The blog covers the problem domain. The documentation will cover Tapix itself -- installation, configuration, every field type, every relationship mode, every lifecycle hook. We are building it as a dedicated docs site, not a README that outgrew itself. **Public beta.** Early access customers will be the first to install Tapix and use it in real projects. We are targeting a closed beta with direct feedback channels before opening it up. The goal is to catch the edge cases that only show up with real-world data from real-world applications. **Features in development.** Some of what we are actively building: - Excel (.xlsx) support alongside CSV, with the same wizard experience - Advanced matching strategies for update-or-create workflows - Custom field type extensions for domain-specific data - Performance optimizations for files beyond 100,000 rows - Expanded Filament integration with inline table actions **More content.** The blog is not stopping. We have posts planned on testing importers, monitoring import health in production, and building importer-specific dashboards. The focus shifts from "how to solve these problems yourself" to "how to solve them with Tapix." [\#](#pricing-reminder "Permalink")Pricing reminder --------------------------------------------------- If you have been reading along and thinking about whether Tapix fits your next project -- plans start at $99/year for solo developers, $199/year for agencies, and $299/year for SaaS and multi-tenant applications. The lifetime deal at $1,499 is limited to the first 50 customers. Every plan includes all features, source code access, and updates. Zero risk: cancel anytime, keep the code, full refund within 14 days. [See current pricing](/#pricing) [\#](#thank-you "Permalink")Thank you ------------------------------------- To everyone who joined early access -- thank you. You bought a product before you could install it. That is the clearest signal we could ask for that the problem is real and the approach is credible. The most useful feedback we have received came from readers who described how their existing importers broke: the CSV that arrived with Spanish column headers, the company name that created 300 duplicate records because the customer re-uploaded the file, the validation error that only appeared in production because the developer never tested with real user data. Those stories shaped what Tapix actually handles. If you want to see where it started, read [Why we're building Tapix](/blog/why-we-are-building-tapix). If you want to understand the full landscape of the problem we are solving, start with [The complete guide to CSV imports in Laravel](/blog/complete-guide-csv-imports-laravel). And if you are ready to migrate an existing importer, [Migrating from Laravel Excel to Tapix](/blog/migrating-laravel-excel-to-tapix) is the practical starting point. We will see you at launch. ### Enjoyed this post? Get notified when we publish new articles about Laravel imports and data handling. Email address Subscribe Almost there — confirm your subscription via email. Related posts ------------- [ Product Jul 10, 2026 Migrating from Laravel Excel imports to Tapix ----------------------------------------------- Step-by-step migration guide: convert your Laravel Excel importer to a Tapix importer with relationships, validation, and a user-facing wizard. ](https://tapix.dev/blog/migrating-laravel-excel-to-tapix) [ Product Jun 30, 2026 How Relaticle CRM uses Tapix for contact imports -------------------------------------------------- Case study: how an open-source Laravel CRM uses Tapix to handle contact imports with company relationships, multi-value emails, and currency parsing. ](https://tapix.dev/blog/how-relaticle-uses-tapix) [ Product Jun 16, 2026 SaaS CSV importers vs self-hosted: which one fits your Laravel app? --------------------------------------------------------------------- CSVBox, OneSchema, and Flatfile are hosted. Tapix is self-hosted. Here's the tradeoff matrix for choosing between them. ](https://tapix.dev/blog/csvbox-vs-self-hosted-import) [ ![Tapix](/img/tapix-logo-light.svg) ![Tapix](/img/tapix-logo-dark.svg) ](https://tapix.dev)CSV and Excel import wizard for Laravel. Product [Pricing](https://tapix.dev#pricing) [Docs](https://docs.tapix.dev) [Blog](https://tapix.dev/blog) [Contact](mailto:hello@tapix.dev) Compare [vs Laravel Excel](https://tapix.dev/vs/laravel-excel) [vs Filament Import](https://tapix.dev/vs/filament-import) Legal [Privacy](https://tapix.dev/privacy-policy) [Terms](https://tapix.dev/terms-of-service) © 2026 Tapix. All rights reserved.