MOTIF — Relationship and sales opportunity interfaces
Every opportunity has a person, a conversation and an unfinished next step. MOTIF connects an Arabic sales board to each opportunity’s record, preserving context as stages and follow-ups change.
Explore the project
1 / 1Project information
- Client
- An original Nextwave project
- Sector
- Professional services
- Platforms
- Web
- Project type
- Business systems
Services delivered
Project overview
A relationship starts with a conversation, but needs more than a name and number to continue. What was requested, who follows up and when should the conversation resume? MOTIF places those daily questions beside the opportunity’s value and current stage.
Follow-up needs more than a pipeline number
Knowing an opportunity’s value does not reveal its next step. A meeting in a separate list may also lose its commercial context. Stages, activities and notes become harder to interpret when their connection is missing.
The opportunity record connects the account, contact and role, owner, value, decision date, stages and activities. The board provides the overview; the record explains what follows and why.
A board for movement, a record for context
Three pages organise a four-stage open-opportunity board, a searchable register and an individual record. The starting workspace contains ten opportunities: eight open, one won and one closed without agreement. Closed records remain in the register and leave the open board.
Cards show account, value, owner and the nearest unfinished follow-up. The detail page keeps stages, activities, notes and decision history beside contact information. Open and won values are separate measures; neither establishes collected revenue.
Explicit probabilities and reasoned decisions
Exploration, qualification, proposal and negotiation use disclosed probabilities of 10%, 35%, 65% and 85%. Each open opportunity’s weighted value is rounded to the nearest cent before aggregation. This is a fixed reading of the board rather than an automated sales prediction.
Winning, closing without agreement and reopening require reasons. A closed result cannot switch directly to another closed result. Activities retain their date, time, type, note and completion state, while register search, filters and visible-row export support review.
Project images
Explore the interface and experience through the project gallery.
1 / 3Use case: turning an initial request into a follow-up
The relationship owner records a clear title, account, contact and role, owner, value, decision date and starting stage. Adding from a board column retains that stage selection. Saving opens the new opportunity record so the next point of discussion can be captured.
A meeting, follow-up call or task receives a date, time and note. It stays with the opportunity and can become the nearest unfinished activity shown on the board. These are user-maintained records: saving a meeting sends no invitation and saving a call places no external call.

Use case: moving a stage and reading its effect
An opportunity worth 420,000 EGP in qualification shows 147,000 EGP weighted at 35%. Moving it to proposal produces 273,000 EGP at 65% while the recorded opportunity value stays the same. The calculation explanation remains accessible inside the record.
Recording a win requires a reason, removes the opportunity from open/weighted totals and adds its value to the separate won measure. If discussion resumes, the owner selects an open stage and records why. Earlier decisions remain in history; changing to a different closed outcome requires reopening first.

Use case: reviewing follow-ups while writing a note
The owner chooses a reading date to review unfinished activities whose dates have passed on open opportunities. A record can show pending, completed or all activities, and a completed item can be reopened. Activities on closed opportunities do not contribute to the open overdue indicator.
An unsaved note remains in the current page while activity filters, reading date or opportunity stage change. Successful saving adds it to the record and clears the input. A storage failure preserves the text for retry. Draft retention applies only to the open page, so saving is required before navigation or reload.

A relationship workspace with a human tone
Plum and raspberry give the workspace a conversational tone, with pale blue for weighted values and soft gold for selected decision contexts. Conversation photography and the next-discussion card place people and actions beside the figures.
The board adapts from four columns to mobile layouts. Four mockups use curved brand-colour backgrounds for the board, register, mobile views and contact detail. Interface lettering remains in the original screenshots, with no text on the backgrounds.

Implemented scope
The work comprises three HTML, CSS and JavaScript interfaces with browser persistence, stage/weighted-value rules, reasoned closure and reopening, activities, notes and exports. Names, accounts and figures are interface records rather than verified company sales or customers. The board, register and opportunity record define the implemented scope; other sidebar modules outline a wider product. Shared operation, permissions, messaging, calendar sync, billing and collection require separate implementation and integrations.
Built with
- HTML5
- CSS3
- JavaScript
- localStorage
Need clearer opportunities and next steps?
We start with your sales stages and follow-up process, then define the records, activities, permissions and integrations your team needs.


