01
Problem Discovery
Identifying the problems SaaS companies face when managing affiliate programs and understanding where existing solutions fall short.
Featured project
Building a SaaS product from idea to production
Founder · Software Engineer · Product Builder
Arkvon is a SaaS platform designed to help software companies build, manage, track, and scale affiliate programs.
I designed and built Arkvon from the ground up, taking responsibility across the product lifecycle, including product strategy, system architecture, backend engineering, frontend development, database design, payment integrations, infrastructure, analytics, SEO, and product design.
Building Arkvon has allowed me to work across the boundaries of engineering, product, design, marketing, and business, giving me experience not only in building software, but in understanding why it needs to be built and how it creates value for users and the business.
Explore Arkvon in a live environment. Create your own account and test the full flow yourself.
Open live demodevarkvon.it.com
Use Stripe test cards to subscribe.
I didn't just build the application. I built the product.
Arkvon required much more than implementing features. I worked through the entire process:
01
Identifying the problems SaaS companies face when managing affiliate programs and understanding where existing solutions fall short.
02
Defining the MVP, prioritizing features, designing pricing, considering different customer segments, and deciding what should be built now versus later.
03
Designing the application architecture, database structure, APIs, authentication, integrations, tracking systems, and business logic.
04
Building the frontend, backend, dashboards, APIs, tracking infrastructure, commission engine, payment flows, and affiliate management functionality.
05
Deploying and maintaining production infrastructure, databases, reverse proxies, SSL, containers, and application services.
06
Implementing product analytics and tracking to understand user behavior, acquisition, and product usage.
07
Working on website structure, content strategy, landing pages, positioning, and SEO to help the product become discoverable organically.
08
Using real usage, technical issues, and business feedback to improve the product and make better engineering and product decisions.
Building the technology behind Arkvon
Arkvon is a real SaaS product with business logic that goes beyond basic CRUD operations. The platform requires tracking, attribution, recurring revenue calculations, payments, payouts, authentication, analytics, and integrations to work together reliably.
Designed and implemented the backend architecture powering merchants, affiliates, campaigns, referrals, commissions, transactions, and payouts. Built REST APIs and the business logic connecting the different parts of the platform.
Designed relational data models for campaigns, affiliates, customers, referrals, transactions, commissions, and payouts. Focused on data integrity, relationships, query performance, and maintaining reliable financial records.
Built the infrastructure required to associate visitors and customers with affiliate referrals and track conversions throughout the customer lifecycle.
Designed commission logic capable of handling different commission models and recurring billing cycles. This required accounting for subscription frequency, commission recurrence, billing cycles, eligibility, and payout timing.
Integrated payment infrastructure and webhook based workflows to connect customer payments with affiliate attribution and commission calculations.
Designed a flexible payout architecture supporting multiple payout providers and affiliate specific payout preferences while maintaining transaction records and payout metadata.
Implemented authentication, authorization, protected resources, validation, and security considerations throughout the application.
Managed deployment and production infrastructure including Docker, Linux, Nginx, SSL, databases, application processes, and production troubleshooting.
Engineering with the business in mind
One of the biggest lessons from building Arkvon has been that good engineering starts before writing code.
That mindset has influenced how I approach architecture and product development. Instead of simply implementing requirements, I enjoy understanding the problem behind the requirement.
Designing the experience, not just the interface
I was also responsible for thinking through the product experience and how merchants and affiliates interact with the platform.
Designing workflows for merchants and affiliates from onboarding through daily usage.
Structuring complex information into interfaces that make analytics, referrals, commissions, and campaigns easy to understand.
Deciding how functionality should be organized so users can navigate the product without unnecessary complexity.
Considering how the application behaves across different screen sizes and devices.
Balancing technical capabilities with simplicity so that powerful functionality does not make the product difficult to use.
I can work with design and product considerations rather than treating engineering as an isolated function.
Thinking beyond the application
Building Arkvon also required thinking about how people discover the product, not just how the product works once they arrive.
Developing search focused content and page structures around problems faced by SaaS companies and affiliate marketers.
Identifying customer pain points and turning them into educational content and acquisition opportunities.
Creating pages designed to communicate the product's value clearly and move visitors toward meaningful actions.
Working through messaging to explain what Arkvon does, who it is for, and why it is different.
Thinking about the journey from search to content to landing page to product to signup to customer.
This demonstrates an understanding of the relationship between technology and acquisition.
Building with feedback, not assumptions
I implemented product analytics to understand how users interact with the platform and where opportunities or problems exist.
I don't just build features. I want to know whether those features actually work.
Taking ownership beyond development
Because Arkvon is my own product, I have also had to take responsibility for what happens after the code is written.
I understand what it takes to get software running in production and keep it running.