Mohammadreza Talebi

NABZ Capital

A bilingual Laravel services platform designed to turn a broad digital need into a structured brief, a trackable reference, and an accountable client journey.

View live siteExplore the project

By Mohammadreza Talebi · 6 min read

nabzcapital.ir
NABZ ecosystem homepage · Live website capture
Year
2026
Role
Product / Full-stack development
Scope
React · Node.js · SQLite
Status
Live

The project, in context

I designed and developed Nabz to turn a broad digital-service need into a structured request and a continuing client relationship. The active Nabz Business product connects its multilingual public website to a Persian project portal, approvals, meetings, documentation, support, and multi-site operations. Nabz Life is a separate private coaching pilot within the wider brand.

A request needs a continuation

Digital-service enquiries often start with a sentence such as 'I need a website' or 'I want to grow my business.' That leaves the real scope unclear. A generic contact form captures a message but does little to connect it to delivery, decisions, and follow-up.

The team's work also extends beyond a single project. Client approval, support, documentation, and tasks across managed sites need a common context and specific access. The platform had to expose useful progress without inventing percentages, treating a proposal as a contract, or showing one client's information to another.

From a brief to a working relationship

The public site explains services through concrete needs and the Nabz Business tracks of launch, growth, and operations. A service explorer lets visitors inspect suggested outputs and prerequisites before carrying selected services into a three-step request. Public content is available in Persian, English, and Arabic; the working client portal is currently Persian.

The request becomes a project record with a reference, stage, milestones, and history. Approvals, meetings, versioned text documents, outcome reports, and support stay attached to that project. A separate operations workspace serves assigned client sites, while the Life pilot follows its own coach and learner relationship rather than being advertised as a completed health platform.

What I built

The parts that make this project useful in day-to-day work.

  1. Services explained before selection

    The public service explorer explains six services, suggested deliverables, and prerequisites. Visitors can select more than one service and continue with those choices in the brief. Dedicated business pages keep launch, growth, and operations from becoming one undifferentiated list.

  2. A brief that survives errors

    The three-step request has field-linked error summaries, a description counter, direct edits from review, keyboard focus handling, and preserved input after a failed send. Server validation remains the final check. The form clarifies intent without presenting the request as an accepted project or a completed contract.

  3. Project progress with a reference

    The project portal uses seven stages, agreed dates, actual milestones, progress, and recorded updates. A proposal is assembled from the project's information and can be saved through browser printing. It does not invent pricing or contractual obligations not present in the record.

  4. Approvals and meetings in context

    Staff can send a deliverable for client approval or revision with a recorded decision. Online, phone, and in-person meetings have confirmation and cancellation states. An ICS export supports manual calendar import; it is not presented as automatic synchronization or push notification.

  5. Documents and results that keep their history

    The text-document centre supports search, categories, immutable versions, archive, restoration, and TXT download. Outcome reports distinguish drafts from published results and retain period, unit, source, and limitations. Clients see only their own published documents and reports.

  6. Support across assigned sites

    Project tickets and conversations sit beside a multi-site operations workspace. Tasks have status, priority, owner, due date, external reference, and internal comments. Support staff are limited to assigned sites; the Icolan and Zerafati connectors provide scoped operational data without storing client administration passwords in the portal.

  7. A separate Life pilot

    Nabz Life implements coach applications, administrative approval, single-use learner invitations, draft and published day-based plans, completion logs, feedback, appointments, and private chat. It is a private pilot without medical services or payments; Zerafati's health intake, nutrition, supplement, store, and exercise-media scope has not been transferred into it.

From structure to release

  1. Make the need concrete

    Service details, selectable outputs, and a reviewed brief help a broad enquiry become something the team can discuss and scope.

  2. Keep decisions with the project

    Milestones, approvals, meetings, documents, and support all use the project as their shared reference.

  3. Separate active products from pilots

    The brand presents Business as the active service product and Life as a constrained private pilot, while other brand directions remain in validation.

Delivery and current scope

  • Persian, English, and Arabic public service pages with prerendered search content.
  • Persian client portal with requests, projects, milestones, approvals, meetings, and support.
  • Versioned text documentation, outcome reports, and scoped multi-site operations.
  • A separately scoped private coach-and-learner pilot for Nabz Life.

Questions about this project

How do Nabz Business and Nabz Capital differ?

Nabz is the parent brand. Business is its active digital-services product; Capital and Home are in validation, while Life is a private coaching pilot. The nabzcapital.ir domain currently hosts the wider service platform rather than a public investment-research product.

What can a client follow in the portal?

Clients can follow their assigned projects, actual milestones, approved dates, deliverable decisions, meetings, published documents and outcome reports, and support conversations. Access is linked to the relevant client and project.

Does a service request include payment or a signed contract?

A request starts discovery and coordination. Public service payments, electronic contract signing, binary attachments, and automatic email or SMS notifications are not part of the implemented service workflow described here.

Have a similar project in mind?

Tell me what you need to build and where the current experience falls short.

Start a conversation+989304330645
Next projectIcolan.ir