Software Engineering & Custom Development

Service Overview

There is a category of operational problem that no off-the-shelf platform solves. A bidding workflow that spans six spreadsheets and four people. A field reporting process that requires data from three systems that don't connect. A client-facing tool that needs to reflect your company's specific workflow, not a generic template. This is where custom development becomes the right answer.

Software Engineering & Custom Development is the workstream that builds what your operation actually needs — not what exists in the market. We scope, design, build, test, and deploy purpose-built tools and applications that live in your workflow, integrate with your existing systems, and do exactly the job they were designed to do.

A Red Grey Principal Advisor owns this workstream for the term of your retainer. They staff it internally across full-stack software engineering. You define the business requirement. We translate it into a scoped build, deliver working software on a monthly sprint cadence, and hand it off with documentation your team can operate and extend.

Start with a Discovery Engagement Talk to Us First →

What This Delivers

Outcomes you can measure. Every month.

Every Engagement begins with a requirements definition and scope. At the end of Discovery, you have a documented specification and a build roadmap. Every month after that, the outcome review ships working software against that spec — not progress updates, not design documents, working software that your team uses.

⚙️

Purpose-Built Tools

Software built for your specific workflow, not adapted from a generic template. The logic, the interface, and the data model match what your team actually does — not what a product manager in another industry imagined.

🔗

Integrated With Your Stack

Custom tools built to connect to your existing platforms through APIs or direct database connections. No new island of data. The custom tool feeds into and draws from the systems your team already uses.

📱

Field and Office Ready

Applications that work on the devices your field and office teams actually use — mobile browsers, tablets, desktop — without requiring special hardware or IT configuration.

📋

Documented and Maintainable

Every build delivered with technical documentation, deployment instructions, and a runbook. Your team can operate it. A future developer can extend it. Nothing is a black box.

🚀

Monthly Sprint Delivery

Working software shipped every month, not at the end of a long waterfall project. Each sprint delivers a functional piece of the build your team can test and use. Feedback is incorporated before the next sprint begins.

🔒

Secure by Default

Authentication, authorization, data encryption, and access controls built in from the start — not added after a security review flags the gap. Every custom application follows Red Grey's security standards.

How We Work

Common workstreams under this service.

These are the most common builds we deliver under Software Engineering & Custom Development. The specific application depends on your operational gap. Discovery defines the requirement, the scope, and the build sequence.

Internal Operations Tools ⚙

→ Build custom web applications for internal workflows that no off-the-shelf platform handles well.
→ Bid tracking, RFI logging, subcontractor management, document routing, approval workflows, and reporting dashboards.
→ Delivered as browser-based applications your team can use without installation.

Field Mobile Applications ⚙

→ Build mobile-optimized applications for field use.
→ Daily log capture, safety checklists, quality inspection forms, punch list management, photo documentation, and progress reporting.
→ Designed for use on a tablet or phone without reliable connectivity.

Client-Facing Portals ⚙

→ Build client portals that give your owners visibility into project status.
→ Document access, change order approvals, and billing without routing everything through your PM's inbox.
→ Define the permission model, the data sources, and the notification rules.

Data Visualization & Reporting Dashboards ⚙

→ Build custom reporting dashboards that draw from your connected data environment.
→ Display the KPIs your principal, your PM, and your finance team actually need.
→ Without waiting for accounting to close or someone to run an export.

Workflow Automation ⚙

→ Identify the manual, repetitive workflows in your operation that follow a consistent logic and automate them.
→ Triggered email sequences, document generation, approval routing, status updates, and notification chains.
→ Build using Zapier, Make, or custom code depending on the complexity.

API and Integration Development ⚙

→ Build custom API integrations between platforms that don't have a native connection path.
→ Define the data mapping, the authentication, the error handling, and the monitoring.
→ Deliver a documented integration your team can operate without engineering support.

The Engagement Process

From the first call to retained delivery. Here is exactly how it works.

Every engagement follows the same sequence. No surprises. No ambiguity about what you're agreeing to before you agree to it.

Scoping Call — 30 Minutes

You describe the challenge. We ask the questions that tell us where the problem actually lives. By the end of the call we tell you which workstream addresses it, what Discovery looks like for this specific problem, and what the first 30 days produce. You leave with a verbal scope and a clear picture of what comes next. No pitch deck. No follow-up sales cycle.

Mutual Non-Disclosure Agreement

Before we review any project data, financials, or internal systems, both parties execute a Mutual NDA. This is a standard two-way confidentiality agreement — it protects your data and our methodology equally. We send it, you review it with your counsel if needed, and we execute before anything substantive is shared. Typical turnaround is one to two business days.

Master Service Agreement

The MSA governs the overall relationship — intellectual property ownership, liability, payment terms, dispute resolution, and termination provisions. It is executed once and covers every Statement of Work issued under it. We provide the standard Red Grey MSA. You review it, propose any changes, and we agree before any work begins. The MSA is the legal foundation. The SOW is the operational scope.

Discovery Engagement — 30 Days

Month one is always Discovery. For Software Engineering, Discovery is a 30-day requirements definition and scoping process. We walk the workflow gap in detail — what triggers it, what decisions are made inside it, what data it needs, what systems it touches, and what the output looks like. We assess the build complexity, identify the integration requirements, and define the acceptance criteria. At the end of 30 days, we deliver a written findings report with a complete requirements specification, a scoped build roadmap, and a month-by-month delivery plan.

Statement of Work

The SOW is issued after Discovery findings are reviewed and accepted. It defines the specific workstreams to be delivered, the success metrics for each, the systems in scope, the communication cadence, and the term. It is signed before month two begins. The SOW is not a proposal — it is the execution document built directly from the Discovery findings. If the Discovery findings don't support a particular workstream, it doesn't appear in the SOW.

Retained Term — Monthly Delivery

The retainer runs on a monthly cadence from SOW execution. Weekly working sessions move each workstream forward. Monthly outcome reviews measure what moved against the baseline established in Discovery. Every month produces a working artifact — a tool, integration, workflow, or process that exists in your operation. Your Principal Advisor signs off on every deliverable. You approve outcomes and success metrics. You do not manage the engineering work.

Scaling Engagements — Scope Change Engagement

The number of concurrent Engagements is set at contract signing and fixed for the term. If your priorities shift mid-term and you need to add or remove a workstream, that requires a Scope Change Engagement — a structured rescoping process that produces updated findings, a revised SOW, and a clear transition plan. The Scope Change Engagement is priced at your original Discovery rate and billed in addition to your current monthly retainer. Changes take effect at the start of the next engagement cycle after the Scope Change Engagement is complete. At contract renewal, your Engagement count can be adjusted with no Scope Change Engagement required.

Runbook & Adoption Handoff

Every workstream closes with a Runbook & Adoption Pack. The runbook documents how the tool or workflow operates, who owns which step, how data quality is maintained, and how to know it is being used. The adoption pack covers staff training, role-level instructions, and what a healthy versus degraded state looks like. The handoff is documented, reviewed, and signed off before the Engagement is marked complete. This is not a PDF filed away. It is the operating manual for the artifact we built.

Systems Access & Security

How we access your systems. What we touch. What we don't.

This work requires access to your systems and data. We take that access seriously. Here is exactly how it works.

What We Access

Access to the systems and data your custom build will connect to — APIs, database schemas, authentication documentation, and existing data exports. We typically need access to the workflows being replaced so we can document the current logic before building the replacement. No production data access is required during the requirements phase; we work from process walkthroughs and sample data.

How Access Is Granted

We request the minimum permission set required for the workstream in scope. Where possible, we use read-only credentials for data review and analysis work. Write access is requested only for the specific systems we are building into. We do not request admin or owner-level access unless the workstream explicitly requires it — and if it does, that is documented in the SOW and requires your written approval before access is granted.

Credential Management

Credentials are stored in a dedicated password manager, never in email or shared documents. Access is provisioned to the named Red Grey engineer assigned to the workstream. Access is revoked at the end of the Engagement or immediately on request. We do not retain credentials after an Engagement closes. If you prefer to provision temporary access per working session, we accommodate that without adding friction to the delivery cadence.

Data Handling

Your data does not leave your systems unless a specific integration or export is part of the workstream scope. Working files used during analysis are stored in a Red Grey client workspace, not in personal accounts or shared drives accessible outside the Engagement team. The NDA governs confidentiality. The MSA governs data ownership — your data is yours. We build on it. We do not retain it.

Communication Security

All client communication runs through a dedicated Slack workspace. Red Grey maintains its own workspace with per-client channels. Your team connects via Slack Connect — you see your channel only, not any other client's. Sensitive documents are shared via a secure link, not as email attachments. We do not use SMS for anything substantive. We do not discuss project data on open channels.

Access Offboarding

When an Engagement ends — whether at term, by mutual agreement, or by early termination — we initiate access offboarding within 24 hours of the final engagement date. All credentials are revoked, all working files are either returned to you or deleted per the offboarding checklist in the SOW, and a written confirmation is issued. You do not need to chase us for this.

Where to Start

Every engagement begins with a 30-day Discovery.

Discovery is not a consulting engagement you buy hoping it leads somewhere. It is month one of a retained workstream. It produces a written findings report. It becomes the foundation of your SOW. If the findings don't support moving forward, you have a clear picture of why and what to do about it — and you are not locked into anything.

Software Engineering & Custom Development — Discovery Engagement

30 days. A complete requirements specification and a scoped build roadmap.

The Discovery Engagement for Software Engineering covers the requirement definition in detail — the workflow gap, the data sources, the integration points, the user roles, the acceptance criteria, and the build complexity. We walk the process with the people who will use the software, document every edge case, and assess the technical feasibility of each option. At the end of 30 days, you have a specification your team has reviewed and approved, and a build roadmap with a delivery timeline by sprint.

Written requirements specification — complete, reviewed, and approved by your team

Workflow gap documentation — what the software replaces and why

Integration map — what systems the build connects to and how

Build roadmap — sprint-by-sprint delivery plan with acceptance criteria per sprint

Technical architecture decision — technology stack, hosting, and deployment approach

Baseline metrics — time cost of current workflow and error rate we'll measure against

Start a Discovery Engagement → See How Engagement Pricing is Structured →

Discovery-Only Hold Policy. If you complete a Discovery Engagement and do not immediately convert to a retainer, your findings remain valid for 90 days. If you return within that window, you convert directly to a retainer with no additional Discovery required. After 90 days, a new Discovery Engagement is required before a retained term begins.

Not sure which service to start with? The scoping call is the right place to figure that out. Tell us what you're dealing with and we'll tell you where to start.

Software Engineering &Custom Development