Skip to main content

Software for companies that run several branches.

Lead routing by territory, one real page per location and a panel the regional managers can read, built for Dallas-Fort Worth operators.

10
Products built in-house
12
Web projects in the portfolio
04
Site languages: EN, TR, ES, DE
UTC+3
Overlaps US mornings and the full EU workday

The metroplex has several centers of gravity: downtown Dallas, Plano, Las Colinas, Fort Worth. A company with branches across them has one website, one phone number and a contact form that sends every enquiry to the same inbox. The branch nearest the customer finds out a day later, if at all.

One real page per location

Each branch gets a page with its own address, phone, hours, staff and the services it actually performs. We will not generate forty near-identical suburb pages to catch searches. Pages like that do not rank for long, and a visitor who lands on one can tell. Where two branches offer the same service, they share a service page and link to each other.

Routing leads to the right desk

A form can ask for a postcode and send the enquiry to the branch that covers it, copy the regional manager and start a response timer. The panel shows each manager only their territory, and a director sees all of them. The same idea works for field crews: a mobile app lists today's jobs, takes photos on site and closes the ticket.

Texas privacy law in the form

The Texas Data Privacy and Security Act covers how a site collects and keeps personal data. Whether your company falls under it is for your counsel. Either way, the consent wording on the form, the retention rule behind it and the people who can read the data should be written down, and we write them down with you.

Working hours

The gap is eight hours in summer and nine in winter. Calls land between 8 and 10 a.m. Central. Written updates arrive each evening our time, which is your morning inbox.

Time difference with Dallas

Dallas hours against Istanbul

Time in the cityIstanbul, summerIstanbul, winterOn our side in summer
08:0016:0017:00Working hours, team online
10:0018:0019:00Evening, handoff notes
12:0020:0021:00Evening, handoff notes
15:0023:0000:00 (next day)Offline, reply next morning
17:0001:00 (next day)02:00 (next day)Offline, reply next morning

How a project runs

From first conversation to launch

Read the full process
  1. Discovery

    We document the business goal, audience, available material, and technical constraints.

  2. Scope

    Pages, features, priorities, responsibilities, and review criteria are written down.

  3. Design

    We establish the interface, component rules, and a CSS design system when the project needs one.

  4. Development

    We implement the approved interface and connect the required panels, CRM functions, or messaging tools.

  5. Quality review

    We review mobile behavior, performance, core accessibility requirements, and technical SEO.

  6. Launch

    The approved release goes live with the agreed support period and content handoff.

Technology used in this work

  • Next.js
  • TypeScript
  • Supabase
  • PostgreSQL
  • React
  • Vite
  • WhatsApp Cloud API
  • n8n
  • Python

Frequently asked questions

How many location pages should we have?

One per branch that has its own address, phone and staff. Suburbs without a branch do not get a page of their own.

Can field staff use it on a phone?

Yes. A mobile app can show today's jobs, collect photos and notes on site, and update the same panel the office uses.

Can we connect it to our existing CRM?

Usually, through its API or an export. We check what yours offers before promising a connection.

Tell us what you need built.

Write the business, the market you sell to and what a visitor should be able to do. We reply with the questions that settle scope.

Chat