Taha Amnay AllamOpen to new projects

I automate people’s problems.

I listen first. Then I scope it, design it, build it end to end and ship it. Anything I end up doing more than a few times becomes an automated pipeline.

See the work Start a project

Six steps, one person.

01Listenclient calls, insights, competition
02Scoperequirements → scope → roadmap
03DesignUX wireframes, the feel of it
04Buildarchitecture, APIs, the whole stack
05Shipcloud, pipelines, DNS, production
06Automatewhat repeats becomes a pipeline

and the last step feeds the next project

No handoff in the middle.

My work sits where product management meets full-stack engineering. The person who listens to the client is the person who writes the code, so nothing gets lost in between.

interviews, the competition, a first wireframe

Product

Listening to clients and gathering insight
Analysing the competition
Turning business needs into a clear scope
UX wireframes
Roadmaps people can act on

Engineering

Ideation and technical architecture
External API integrations
Cloud hosting
Automated pipelines
DNS and production deployment

Whatever the problem needs.

01
SaaS platforms
Products with AI at the core, from the first user story to paying customers.
JawblyRuddud
02
CRMs and portals
Case management, partners, documents and the automations around them.
03
Custom websites
Fast, multilingual sites, hosted, maintained and kept indexable.
04
Video automation
From a topic to a scripted, voiced, rendered short, scheduled and published.
The Bear ThinksClip pipelines

I build products.
I also build leverage.

Anything I do more than a few times becomes an automated pipeline. Each one is wired to the services it needs through their CLIs, APIs and MCP servers, so a multi-step job runs end to end without me in the middle. My own time goes to product thinking, architecture, and making the thing look and feel great to use.