Rasid / Independent product · B2B SaaS
A clearer working day for collections teams.
Building an Arabic-first product for customer follow-ups, receivables, and team coordination—with AI assistance inside the workflow.
- My role
- Independent product builder; product, UX & technical delivery
- Period
- 2026 · Active development
- Status
- Private testing & commercial validation
Follow up.
Record.
Keep moving.
Arabic & English · Offline support · Team workflows
The problem worth solving
Customer follow-ups and collections can be spread across spreadsheets, WhatsApp conversations, and people’s memory. As a team grows, keeping a clear record of who needs a call, what was promised, and what has been paid becomes harder.
Rasid grew from a payment-follow-up app into an Arabic-first B2B product. The central idea is a working day organized around the next customer action, with the payment record and relationship history close at hand.
What I’m building and leading
I independently built the product across product strategy, UX, architecture, implementation, testing, deployment, and monitoring, using AI-assisted development. I’m now leading a team through private testing and commercial validation to inform product priorities and launch planning.
The product brings customer follow-ups, payments, reminders, team assignments, reporting, and AI assistance into one bilingual workspace. Visit the Rasid website ↗
Product decisions that shape the experience
Build for Arabic from the start.
Arabic and English have complete interfaces with right-to-left and left-to-right layouts. Language influences the workflow and communications as well as the labels.
Keep the day’s work actionable.
Daily follow-ups, payment recording, and reminders sit alongside the customer’s history. Teams can keep the next action connected to the context behind it.
Keep access tied to responsibility.
Organizations and team roles have access controls enforced in the database. Agents work with their assigned customers, while managers coordinate the wider team.
Plan for imperfect connectivity.
An installable app and offline write queue support work when the connection drops, with changes synchronized when connectivity returns.
Put AI inside practical tasks.
AI features help with call planning, questions about customer data, reminder drafting, and other collections tasks. The product replaces identifying customer details before sending supported AI requests to the model provider.
Where the product is today
The public website is live at rasids.com. Access to the application is controlled while testing and commercial validation continue.
This is the current evolution of the payment app featured on my earlier personal website. Rasid now has its own identity, product site, and a broader team-based workflow.
The next product decisions are being shaped by testing and commercial validation. I’m treating launch readiness and product priorities as part of the same work.
Explore Rasid ↗Under the hood
React and TypeScript on the front end; Supabase and Postgres for authentication, data, and access control; server-side Gemini integrations for AI features; Cloudflare Pages for hosting. Offline support, monitoring, and analytics are part of the product’s delivery infrastructure.
My role is to connect these technical choices to the business workflow, user experience, and requirements of running a product with multiple organizations.
Next project