Skip to content
Service

Web design & development

Marketing sites designed as products: clear journeys, an editable CMS, and performance treated as a feature.

Web design & development

A website is not a stack of pages to decorate. It is a path: someone arrives, understands, and knows what to do next. We design and build that path as a product — research before the first layout, a system that can grow, and front-end work that treats speed and clarity as part of the design, not a later repair.

Too many sites look finished and still fail the simple jobs: find a service, understand a price, write a message, switch a language. We start with those jobs, and with the content you actually have, so the design is not a pretty frame around missing text.

Built to be edited, and to stay fast

Every site we ship has a content layer your team can use without waiting for a release. We also agree a performance budget early, because a campaign image or a new script should be a visible decision, not a quiet weight that appears after launch.

From our studio in Homs we build for Arabic and English together when both are needed, and we stay through launch and a short period of care so the first weeks in the real world are not yours alone.

Who it is for

Problems this work solves

These are the patterns we see before we begin. We name them plainly so the scope of the work can be honest.

Finished, but quiet

Marketing sites that look finished and still do not produce conversations.

Waiting on a developer to change a line

Teams stuck waiting for a developer every time a line of copy changes.

Arabic squeezed into an English grid

Bilingual companies whose Arabic pages feel squeezed into an English layout.

A public site as careful as the product

Products that need a public site as careful as the product itself.

Scope

What the work includes

Clear pieces that belong in the phase, written so you can see what the work covers.

UX research & wireframes

Structure first: what the visitor needs to do, and in what order.

Design system in Figma

Components and type that stay coherent as the site grows.

Front-end development

A careful build that holds typography, motion, and RTL with equal care.

CMS integration

The team can change copy and pages without waiting on a developer.

Performance & SEO foundations

A site that loads cleanly and can be found, without invented rankings.

Analytics & conversion tracking

A clear view of what people actually do once they arrive.

Approach

A clear path from the first week

A sequence we return to on every project, with the title and the full description written in the open.

  1. Map the journey

    Goals, sitemap, and the pages that have to work hard — contact, pricing, a service, a story.

  2. Design the system

    Type, colour, components, and layouts for every breakpoint, in Arabic and English when needed.

  3. Build and connect

    Front-end, CMS, forms, analytics, and a performance budget the team can keep.

  4. Launch and settle

    QA, go-live, a short period of care, and a handover your team can edit without us.

Deliverables

What you leave with

Files and reviews you can keep working with after handover — not a presentation that ends in the last meeting.

  • A designed and built site

    The pages you need to launch, on a system that can grow.

  • An editable content layer

    So marketing can change copy and media without a release.

  • Forms, analytics, and care

    Enquiries that arrive, and a clear view of what happens next.

  • A performance baseline

    Lean assets and a budget written down, not hoped for.

Practical notes

Timeline and tools

General ranges for a typical scope. The final timetable is written after a first conversation, according to the size of the work.

Typical timeline

A marketing site of a clear scope often takes a couple of months from the first map to launch. Smaller first phases — a home, a service, a contact path — can be shorter when the content is ready.

Tools

  • Figma for the design system and page layouts.
  • A CMS chosen for the team that will actually edit it.
  • Analytics and form notifications wired before launch, not after.
Why ReachUp

A studio nearby, and a scope written plainly

We work from Homs, author Arabic and English together, and keep design and build in one team through handover.

  • A studio in Homs

    We are a studio based in Homs, Syria — close to the markets we design for, and easy to talk to.

  • Two languages, authored together

    Arabic and English are authored together, not treated as a late translation.

  • Scope written plainly

    Scope and timelines are written plainly, including what the work does not include.

  • Design and build in one team

    Design and build sit in one team, so the file you approve is the file that can ship.

  • We stay for the handover

    We stay for the handover: a kit, a walkthrough, and a clear path for the next phase.

FAQ

Questions we hear about this work

Direct answers to what is usually asked before the work begins.

We can. Many clients come with a draft; we tighten it, or we write from the strategy when needed.

The one that fits the team. We often ship a custom CMS, and we also work with familiar tools when they are the right fit.

We design for that from the start: lean assets, a sensible host, and a performance budget we actually keep.

Yes, when you want us to. A short care period is part of launch; longer stewardship can be agreed as a next phase.

Yes. We start by reading the current journey and the pages that already work, so we do not throw away what is useful.

The layout, type, and CMS are planned for both from the first templates, not as a translation pass at the end.

Is this the right service for you?

Tell us about the product or the brand, and we will come back with a clear first-phase plan.