Select Interactive

Operations Software

Operations software for teams still running the business in Excel.

Manufacturers’ representatives, internal sales forecasting groups, and professional firms whose system of record is a shared workbook. We replace that with role-scoped web apps: governed manufacturer data, 5-year forecasts, employee compensation portals, employee intranets. Senior in-house. You own the code. Alcon, MJEC, Rees-Jones Holdings, JTaylor.

What is still living in a spreadsheet?See the work

Who This Is For

Who we build operations software for

  1. 01

    Manufacturers’ representatives

    Coordinating 100+ lines across territories. MJEC: HVAC, mechanical, building systems; 125+ manufacturers and partners.

  2. 02

    Internal sales and data-science teams

    Forecasting revenue off shared workbooks. Alcon: global eye-care, where a single change to the workbook took 30–60 minutes.

  3. 03

    Multi-practice firms

    One employee home with strict roles (JTaylor intranet).

  4. 04

    Field staff

    People who need a brochure or a number now, not a ticket to marketing or finance.

Not for

Generic “digital transformation” programs, or Power Apps implementations.

Domain Problems

Domain problems we keep seeing

The workbook is the bottleneck

  • Alcon: shared Excel, 30–60 minutes per change. Replaced with a real-time app: role-scoped product data, sales history, notes on each change, forecasts up to 5 years. Built with Alcon’s data science team.
  • Rees-Jones Holdings: condensed complicated Excel documents into user-friendly interfaces backed by real-time databases.

Partner and line data lives in five places

  • MJEC: contacts, contracts, locations, divisions, target vs. actual sales, notes, documents, centralized. Audit log (who, what, when). Seven-day database snapshots.

Field people cannot wait on headquarters

  • MJEC client tool: filter by location, equipment, or product, then generate a live-data PDF brochure in seconds. Same auth layer as the internal app.

Everyone in the firm needs a different door

  • JTaylor: every employee, practice-specific content, nothing they should not see.
  • Rees-Jones Holdings: role type decides the experience and the data. Employees, managers, directors, executives, HR, C-suite, and IT each get a different interface and different access.

This is a product you keep, not a project you archive

  • MJEC: launched 2025, quarterly review and release cadence.
  • Rees-Jones Holdings: launched 2024, ongoing. Multiple phases, with feature enhancements and new features each year.
  • JTaylor: a decade.
  • Alcon: a platform the internal team uses, not a one-off dashboard dump.

How We Work

How an operations engagement runs

Map the real objects before UI. Role design is architecture, not a settings screen.

Manufacturer, territory, SKU, forecast version, employee role, before screens.

Alcon: per-user and region data. MJEC: Firebase RBAC across two apps. JTaylor: practice-gated intranet.

Stakeholders click their own data, not a slide.

Optional quarterly partnership (MJEC’s actual cadence). Enterprise web development covers SSO, systems of record, and agent-ready handoff (OpenAPI, llms.txt, MCP).

Work

Operations software we have shipped

See all work
Forecasting platform

Alcon: Revenue Forecasting

Excel to real-time. 5-year horizon. Role-scoped product data and sales history. Built with Alcon’s data science team. shadcn charts.

View case study

30–60 min

Excel change, now seconds

  • Products, history, and revenue models in PostgreSQL
  • Role-scoped views per user and region
  • Notes on each change; forecasts up to 5 years
Rep firm operations

MJEC

Operations software for a manufacturers’ rep firm: 125+ lines, an internal app plus a field brochure tool. Azure + Firebase. Quarterly releases.

View case study

125+

manufacturer lines

  • Centralized contacts, contracts, locations, and sales
  • Live-data PDF brochures for the field
  • Audit log and seven-day snapshots
Firm-wide ops

JTaylor intranet

A firm-wide intranet in daily use by every employee, with practice-gated content and role-based access.

Everyemployee

View case study

Technology

A conventional stack your team can hire for

Alcon

  • TanStack Router
  • TanStack Query
  • React
  • TypeScript
  • Vite
  • Zod
  • shadcn/ui
  • Tailwind
  • PostgreSQL

MJEC

  • TanStack Start
  • TanStack Router
  • TanStack Query
  • TanStack Table
  • TanStack Form
  • React
  • Vite
  • shadcn/ui
  • Tailwind
  • Firebase
  • Zod
  • Nitro
  • Azure

FAQ

Questions operations teams ask

Yes. MJEC owns a dual-platform system SI built and still iterates quarterly. You own the code.

Alcon was built alongside their data science team: products, history, revenue models, market data.

It stops being the system of record. History is modeled in a real database. People get a role-scoped UI.

No. MJEC’s tools are web, including mobile workflows. We do not build native iOS or Android.

You own a conventional React and TypeScript codebase your team can hire for. The difference is ownership and fit, not a cost comparison.

Yes. That is the enterprise path. See Enterprise web development.

Keep Going

Related services, process, and reading

Services

Company

Reading

Start A Conversation

What is still living in a spreadsheet?

Objects, roles, and who is blocked in the field. A technical conversation, not a pitch.

Start a conversation
All industries