Build it, fix it, or join your team.
Three ways to work with us. The same two engineers do the work in all of them.
Nothing is built yet
You have an idea, a process that lives in spreadsheets, or a product that needs its first version.
We design it in Figma, build it, and put it in front of the people who will use it.
What you get
- Product design in Figma
- A working web app, dashboard or mobile app
- AI features where they earn their place: assistants, transcription, automation
- The code, documentation and accounts, handed over to you
How long it takes
Recent first versions were ready to review in two to three weeks. The written plan gives you the date for yours.
How it’s priced
A fixed price for each phase, agreed in the written plan before that phase starts.
Examples
- Crowdsky
A co-pilot for drone pilots: where to fly, where not to, and an AI assistant for planning flights and editing footage.
- LiveLink
Staffing, logistics and crowd management for large events in Saudi Arabia.
- Mozn LMS
A learning platform for Saudi schools: timetables, attendance, lesson preparation and reports.
“The final demo is polished, functional, and investor-ready — exactly what we needed. Ahmad is detail-oriented, communicative, and solutions-focused.”
Crowdsky, Upwork review, June 2025
Something is broken
Your app is slow, falling over, or was built by someone who has moved on. Maybe it came out of a no-code tool or an AI app builder and has hit its limits.
We find out why, fix what’s urgent first, then make the rest solid.
What you get
- A written audit covering code quality, performance, security, scaling and integrations
- A list of fixes in priority order, with what each will take
- The fixes themselves, most urgent first
How long it takes
Small fixes usually take one to two weeks. Larger clean-ups take four to eight.
How it’s priced
Small and urgent fixes are billed by the hour. Larger clean-ups are a fixed price, quoted from the audit.
Examples
- Movemeback
We upgraded the app from Angular 14 to 19, fixing the type and import breakages the upgrade exposed.
A surfboard marketplace whose own Angular upgrade had failed: we fixed its Firebase errors and moved it to Angular 20 with server-side rendering.
A legacy PHP ERP: we moved its screens and business logic into a new Angular front end.
“Ahmad did excellent work. He quickly gave me an overview of the problem and the potential solution once I gave him access. He is technically very sound, doesn’t complicate things and effectively communicates everything required.”
Hamza D., Upwork review, December 2023
Your team needs another senior engineer
You have a product and a team. You need a senior Angular or React engineer for a few months, or a second opinion on architecture before you commit to it.
One of us joins your repository, your meetings and your process.
What you get
- A senior engineer working inside your team
- Architecture reviews and technical due diligence
- Advice on the stack before you build on it
How long it takes
One month minimum, then month to month.
How it’s priced
A monthly rate for the days each week you need, billed month to month.
Examples
- Trust Event Solutions
Full-time Angular engineering inside Trust’s team, on their event registration software.
A Swiss SaaS for scaffolding and construction planning: long-term Angular front-end work on its planning dashboards and workflow components.
A venture-backed product studio: maintaining its Angular apps and building new ones.
“Willing to deeply understand the code base and offer solutions. Very helpful in handling a new project that he was not in from the start.”
Trust Event Solutions, Upwork review, March 2025
What we work with
We choose the stack for the job, and we’ll tell you why. These are the tools we reach for most.
- Front end
- Angular, React, Next.js, Vue, TypeScript
- Back end
- Node.js, NestJS, Django, Python, REST APIs
- Mobile
- React Native, progressive web apps
- Data
- PostgreSQL, MongoDB, Firebase
- Infrastructure
- AWS, Docker
- AI
- LLM integrations, assistants, transcription, TensorFlow
- Testing and automation
- Selenium, Scrapy
- Design
- Figma
What happens after you book
A 15-minute call
You tell us what you’re building or what’s broken. We ask questions until we understand the job.
A written plan
Scope, approach, timeline and cost, in plain language, within three working days of the call.
Short sprints
We build in sprints of one or two weeks and show you working software at the end of each one.
Launch and handover
The code lives in your repository from the first commit, the accounts are in your name, and the documentation is yours.
Support, if you want it
We stay on for fixes and improvements, or hand everything over to your team.
Questions people ask first
Can you take over an app someone else built?
Yes. We start with an audit, so you know what you have before you spend more on it: what’s solid, what’s fragile, and what to fix first.
Our app was built with a no-code tool or an AI app builder. Can you help?
Yes. We’ve worked with apps built on tools like Bubble and Zapier, and we fix React front ends generated by Lovable and Bolt. Sometimes the right fix is inside the tool; sometimes it’s moving the app to code you own. The audit tells you which, and what each would cost.
What’s in a technical audit?
Code quality, performance bottlenecks, security problems, how it will cope with more users, and how well its integrations hold up. You get a written report with fixes in priority order and what each will take.
Do you work on the front end and the back end?
Yes. Our deepest experience is in front ends, especially Angular and React, and we build the back ends, databases and integrations behind them.
How do you charge?
New products are a fixed price for each phase, agreed in the written plan. Small and urgent fixes are billed by the hour, and larger clean-ups are quoted from the audit. Joining your team is a monthly rate. Each phase is invoiced half at the start and half on delivery.
Who owns the code?
You do. The code lives in your repository from the first commit, the accounts are in your name, and everything we make for you is yours once it’s paid for.
What hours do you work?
Monday to Friday, 9:00 to 18:00 Pacific time, from Faisalabad, Pakistan. Pakistan is UTC+5: an hour or two ahead of the Gulf and three to five hours ahead of Europe, so we can also meet in your working day. We’ve worked to UK, Irish and Swiss clients’ hours before.
Tell us what you’re building, or what’s broken.
A 15-minute call with Ahmad. You’ll be talking to an engineer, not a salesperson.
Or email ahmadfiazjan@forclev.com, or call +1 (321) 550-5720.
Ahmad works Monday to Friday, 9:00 to 18:00 Pacific time, from Faisalabad, Pakistan.