opengate
Start a project

Command

Accounts, delivery and people.One place to run them.

The morning, in one sentence.

Command opens on a short brief: what changed and what to do today, ranked by how soon it matters. Below it, each section gets one line with its figure and its state in words.

The brief, then every section

The brief ranks what to do now, today and later. Each section under it gets one line: the figure, and in words whether it needs you.

Ranked by how soon it matters

Each action carries its urgency as a word and a colour. The reason is written under it, so nobody has to open the section to learn why.

One line per section

A section shows its headline figure and its state in words. The figure itself is never coloured. The word beside it says what is wrong, so nobody has to guess which number is the problem.

Each role sees its own part.

Exec, sales, marketing and engineering each open their own screen. What a role may not see is removed on the server, before the page is sent.

Questions to the company's documents: opengate Assistant

Sales opens sales

A sales login lands on the accounts, the tasks and the tender radar. The people register and the systems never reach its browser.

One register for access

Every login, its role and its state are in one list. Suspending a person is one change in one place.

Every account, with its next action.

Each account shows its owner, the next action and when it is due, active projects and the contracted sum per currency. An account with work under way and no next step is flagged.

Flagged accounts first

Accounts that need a next step rise to the top. Website leads from the last 30 days are in a pane beside them, so a new request never waits in another tool.

The attention flag

An account with active delivery and no next step ahead is flagged beside its name. An overdue next step raises the same flag.

Leads beside the accounts

Every website form lands next to the accounts, with who sent it, the company and the form it came from.

Tasks, projects and what blocks them.

Tasks are on a board by status and belong to projects. A task that waits on another names it, and the timeline lays every task out from start to due.

A board by status

Backlog, in progress, blocked and done, for a team or for one project. Each card carries its owner.

What waits on what

A task can wait on another. The timeline sets each task from start to due, with the task it waits on named beside it.

Hiring, the team and the hours.

Each opening shows its applicants by stage, the team and the contractors share one list, and hours are logged against clients and projects.

An opening and its applicants

Each opening shows its applicants by stage, from new to offer, with the next step for each.

Hours against clients

Each person logs time against a client and a project, so a week of hours adds up both ways.

Search, traffic and speed, from every engine.

Google, Yandex and Bing report clicks and impressions side by side, next to the analytics counters. Field vitals from real visits are shown against the lab scores, with the last deploy below.

Every engine in one table

Clicks, impressions, click rate and position from each webmaster console, for the same week, with the visits behind them.

Real visits against the lab

Loading, response and layout shift measured on real visits at the 75th percentile, beside the lab score for the same pages.

Every automation, and when it last ran.

Each scheduled job reports whether its data landed and how long ago. A stale job also says how soon someone has to act on it.

Freshness against a response tier

A healthy job shows its age alone. A stale one shows its tier: start now, today or the next working day.

Integrations, checked or declared

Every connected system is listed with what it is used for, and whether a live check confirms it or it is only declared.

Tenders, scored for fit

Public tenders are read and scored against what the company builds, so the few worth a response rise to the top.

Every edit, with who and when.

A change to an account, a task or a person is recorded with the field, the value before and after, who made it and when. Archiving takes a record off the list and keeps its history.

Was and now, side by side

The old value stays readable beside the new one, so a changed sum or a moved due date is never lost.

One account's history

The same record, read for one account, lists every change it has had in order, with the person behind each.

Run your company from one screen.

Tell us which accounts, projects and people your company runs on, and who needs to see what. We build the screens around that.

Start a projectBook a call