HelloHafez, Imagination Built Into Software
العربيةSend an idea

IDEAS IN MOTION · BUILT IN AMMAN

ODD IDEAS. USEFUL SOFTWARE.

From Amman, HelloHafez turns everyday problems and slightly strange ideas into clear products you can see and try.

Follow the projects Send a rough idea
HelloHafez studio artwork with colorful paths and people moving toward a new product
Different pathsOne useful product

Five connected projects

Five problems close to home. Five products built to handle them.

See the work

Each project begins with a real problem in books, team work, sales, invention, or reviewed AI work. Follow the route from problem to useful screen.

A PRIVATE GIFT

Congratulations. You have a free private consultation.

Tell Ahmad what is stuck, what you are considering, or where you want a second pair of eyes.

PRIVATE TO YOUThis request goes privately to Ahmad and is never posted publicly.

The projects first

See the work before the details.

View from the Rawi project
01 / 05RawiRead every detail full size Open project

A quick question

What is wasting your team’s time?

Write the rough version. It can be one problem, one repeated task, or one idea that has stayed stuck.

Already on the table

Five projects. Real screens. One studio in Amman.

  1. 05Projects shown

    Books, team work, sales, invention, and reviewed AI.

  2. REALInterface proof

    The screen comes before the explanation.

  3. AR + ENTwo complete routes

    The same structure in both languages.

  4. AMMANBuilt from here

    Jordan first. The region next.

01Books + AI

See the product first

Rawi

A book search that begins with a sentence, not a filter.

Screens from the real interface

Rawi

The interface is real. Records shown in preview or demo views may be illustrative.

01 / 02Compare the books with their covers

Rawi

Compare the books with their covers
Rawi real interface showing book results with covers, titles, and recommendation details

Compare the books with their covers1 / 2

Try the interactive walkthrough
Book search preview
English + عربي

Reader says

I want an Agatha Christie mystery with travel and atmosphere.

A natural request can include a mood, subject, language, or budget.

MysteryTravelAgatha Christie
Cover of Death on the Nile (Poirot)

Rawi recommends

Death on the Nile (Poirot)

Agatha Christie

A classic mystery with a vivid setting and a full cast, for a reader who wants atmosphere as well as a puzzle.

View the book at Legenda

The recommendation includes the book, not only an answer.

Why it exists

Most catalog searches begin with filters. Readers often begin somewhere less tidy: a mood, a memory, a price limit, or the kind of evening they have in mind.

  1. 01

    What gets stuck

    A reader can know what they want to feel without knowing the title, author, or shelf where the right book lives.

  2. 02

    What the product changes

    Rawi treats the full sentence as the search. It reads the intent, stays inside Legenda's catalog, and returns book cards that are easy to understand and compare.

  3. 03

    What becomes easier

    A vague thought becomes a real book choice without asking the reader to learn the catalog first.

What the screens show

  1. 01
    Sentence search

    Ask naturally in English or Arabic instead of filling in filters.

  2. 02
    Book-first result

    See the cover, title, author, and reason for the suggestion.

  3. 03
    Catalog boundary

    Recommendations stay inside the books Legenda can verify.

  4. 04
    Useful constraints

    Add a mood, subject, language, author, or budget to the request.

  5. 05
    Bilingual path

    Move between English and Arabic without changing how the search works.

Back to projects
02Team operations

See the product first

Legenda Task Dashboard

Due date, owner, decision, and pressure, together on one screen.

Screens from the real interface

Legenda Task Dashboard

The interface is real. Records shown in preview or demo views may be illustrative.

01 / 03Read the day in one executive brief

Legenda Task Dashboard

Read the day in one executive brief
Legenda Task Dashboard real interface showing the executive brief

Read the day in one executive brief1 / 3

Interactive work map

How the day becomes a clear decision

Choose a step to see how the dashboard carries work from the morning brief to the report.

Current step

Brief

Collect the day into one readable operating view.

Useful result

One clear place to begin the day.

Why it exists

Built for UBCC and Legenda around the questions that interrupt a working day: What is due, who owns it, what is blocked, and what needs a decision now?

  1. 01

    What gets stuck

    When tasks, approvals, and updates live across chats and separate files, the team spends too much time rebuilding the picture of the day.

  2. 02

    What the product changes

    One connected workspace brings the daily brief, work board, approvals, and reports into the same operating view.

  3. 03

    What becomes easier

    People can open the dashboard and understand the next move without asking someone else to translate the situation first.

What the screens show

  1. 01
    Executive brief

    See the day's pressure, decisions, and ownership at a glance.

  2. 02
    Work board

    Follow active work by owner, due date, priority, and next action.

  3. 03
    Clear ownership

    Keep one responsible person attached to every piece of work.

  4. 04
    Approvals

    Hold decision points in view instead of losing them in chat.

  5. 05
    Reports

    Turn completed work and open pressure into a useful management view.

Back to projects
03B2B sales

See the product first

B2B Tracker

A sales tracker built around the next action, not data entry.

Screens from the real interface

B2B Tracker

The interface is real. Records shown in preview or demo views may be illustrative.

01 / 03See every active relationship

B2B Tracker

See every active relationship
B2B Tracker real interface showing active relationships across the sales pipeline

See every active relationship1 / 3

Interactive relationship map

How an account keeps moving

Choose a step to follow one business relationship from its account record to a visible decision.

Current step

Account

Start with one company and one clear relationship record.

Useful result

The relationship has one place to live.

Why it exists

The UBCC / Legenda B2B view reflects how relationships in Jordan grow through context, timing, and careful follow-up. A list of company names is not enough to protect that work.

  1. 01

    What gets stuck

    After several calls, meetings, and book-list requests, the real state of a relationship can disappear inside scattered notes.

  2. 02

    What the product changes

    Each account keeps its owner, stage, recent context, and one clear next action together, from first contact to proposal.

  3. 03

    What becomes easier

    The next follow-up begins with the relationship already understood, not with another round of reconstruction.

What the screens show

  1. 01
    Account detail

    Keep the people, segment, notes, and current opportunity together.

  2. 02
    Next action

    Give every active relationship one visible move and owner.

  3. 03
    Relationship history

    Return to the calls, meetings, and promises that shaped the account.

  4. 04
    Pipeline

    See which relationships need contact, a meeting, or a proposal.

  5. 05
    Book-list context

    Keep reading needs and offer details close to the conversation.

Back to projects
04Creative R&D

See the product first

Inventors R&D Loop

Turn an unclear idea into a small test that can teach you something.

Idea labMove the idea, do not decorate it
01 / 08

Current move

Frame

What is the real problem?

Do

Write one sentence without describing a solution.

Leave withA problem worth solving

Continue, change direction, connect it to another idea, or stop.

Why it exists

New ideas usually arrive as a mixture of instinct, excitement, and assumptions. The loop gives that energy a shape without making it feel like paperwork.

  1. 01

    What gets stuck

    A promising idea can stay too large and too vague to test, which makes every conversation about opinions instead of learning.

  2. 02

    What the product changes

    Eight moves help frame the question, scout what matters, strip the idea down, shift perspective, combine pieces, find weak points, build, and test.

  3. 03

    What becomes easier

    Each pass ends with a clear choice: continue, change direction, connect it to another idea, or stop.

What the screens show

  1. 01
    Frame

    Name the real question before looking for a polished answer.

  2. 02
    Scout

    Look around the idea for useful references, limits, and surprises.

  3. 03
    Strip

    Remove everything that is not essential to the first test.

  4. 04
    Build

    Make the smallest version that someone can react to.

  5. 05
    Test

    Use evidence from the test to choose the next direction.

Back to projects
05Reviewed AI work

See the product first

TanDamn

Fast work, separate judgment, and visible evidence in the same room.

TANDAMN // REVIEW ROOMOne mission, separate roles, a visible decision
PUBLIC-SAFE TOUR
FICTIONAL PRODUCT TOURHuman decision required
Sample mission

Review a supplier onboarding flow

Check the flow before it reaches a live supplier.

Builder09:12

Prepared the supplier onboarding flow and attached the walkthrough and consent wording.

Evidence attached
Independent reviewer09:18

The consent step can still be misunderstood. Keep this concern visible before approval.

Disagreement stays visible
Builder09:24

I clarified the wording and attached the revised step as new evidence.

Evidence attached
Decision owner09:27

Mission on hold. I will review the change and the challenge before releasing it.

Human decision required
Human decision gateHuman decision required

The exchange reaches this gate. The final decision stays with a person.

FICTIONAL PRODUCT TOURHuman decision required
Sample mission

Review a supplier onboarding flow

Check the flow before it reaches a live supplier.

Builder09:12

Prepared the supplier onboarding flow and attached the walkthrough and consent wording.

Evidence attached
Independent reviewer09:18

The consent step can still be misunderstood. Keep this concern visible before approval.

Disagreement stays visible
Builder09:24

I clarified the wording and attached the revised step as new evidence.

Evidence attached
Decision owner09:27

Mission on hold. I will review the change and the challenge before releasing it.

Human decision required
Human decision gateHuman decision required

The exchange reaches this gate. The final decision stays with a person.

Phone detailThe disagreement in sequence

The builder answers the independent review with evidence, while the decision owner keeps the mission on hold until the concern is resolved.

Follow the builder update, independent challenge, evidence reply, and human hold in order.

Why it exists

When an AI system both does the work and declares it correct, speed can hide weak reasoning. TanDamn makes the review part of the product, not an afterthought.

  1. 01

    What gets stuck

    Complex work becomes difficult to trust when the build, the check, and the final decision blur into one invisible process.

  2. 02

    What the product changes

    A builder advances the work, an independent reviewer challenges it, evidence stays attached, and a person makes the final decision.

  3. 03

    What becomes easier

    The final call keeps its reasoning, disagreements, and supporting evidence visible enough to inspect.

What the screens show

  1. 01
    Command board

    See active operations, review state, and decisions in one view.

  2. 02
    Separate roles

    Keep the builder and reviewer from silently becoming the same voice.

  3. 03
    Evidence trail

    Attach the material used to support or challenge the work.

  4. 04
    Visible disagreement

    Hold conflicting assessments open until someone resolves them.

  5. 05
    Decision room

    Give the final human call a clear place and recorded reason.

Back to projects

Inside the studio

Built in Amman to move an idea into a product people can use.

HelloHafez is an independent product studio in Amman. It starts with problems close enough to notice properly: finding a book, keeping a team aligned, following a relationship, testing an invention, or reviewing complex AI work.

Books, films, visual culture, and code shape how the studio explains, looks, and moves. Fast, hands-on coding helps an idea move from sketch to working screen. The final standard stays practical: can someone understand it, use it, and know what happens next?

  • 01See the problem clearly

    Start with the real work and the people who face it.

  • 02Try something real

    Move from talk to a working screen people can question and try.

  • 03Know the next move

    Keep what helps, remove what confuses, and decide what comes next.

  1. 01
    Observe

    Start with the real problem, not a feature list.

  2. 02
    Make

    Turn the idea into something people can click, question, and test.

  3. 03
    Refine

    Keep the useful part, remove confusion, and make the next move clear.

THE ROUTE STARTS HERE

From Amman, for ideas ready to travel.

AMMAN · JORDAN · BUILT FOR THE REGION

Send the problem before you polish the pitch.

Bring the rough idea. Leave with a clearer next move.

You do not need a polished proposal. Send the problem, who faces it, and what you wish worked better. A sentence, sketch, or screenshot is enough to begin.

The first conversation is about the problem, the people who will use the product, and the smallest useful version worth testing.

  1. 01

    Tell us where the work gets stuck

  2. 02

    Show us whatever exists today

  3. 03

    Shape the smallest useful first version

Put the rough idea on the table.

It goes straight into Ahmad's private studio inbox. A clear problem is more useful than a polished pitch.

Your message is private studio correspondence. Read how it is stored.