Enterprise software development

Enterprise software development that connects to the systems you already run

We map your ERP, identity provider and data warehouse first, then build the new software to fit them and roll it out one site at a time.

Get your enterprise software scoped in writing
Trusted by the world's fastest-growing brands

What enterprise software is

Software that fits an organization with many moving parts

Enterprise software development builds applications for organizations with many teams, existing platforms and a security group that reviews the result. The work is mostly about what the software connects to and who may do what in it.

Order approvalsSigned in with SSOPO 40-1187 · Columbus$18,420.00From the ERP · Oct 8, 9:31 a.m.Approval chain · 3 roles14 approversSite managerApproved 9:42 a.m.FinanceReturnApproveOperationsAfter finance

Connected first

The ERP, the identity provider and the warehouse are mapped before design starts, so the new software reads from them and writes back to them.

Ready for review

Your security and procurement teams get the answers in writing: where data lives, who can reach it and what is logged.

Rolled out in stages

One site or department goes first, and the next group waits until you approve each stage.

Two ways in

Build around your platforms, or buy a package

The right one depends on what your current systems do well and how your processes differ from the package.

Packaged softwareAdopt a vendor’s platformCustom buildKeep the core, build what is missing
Starting pointThe old systems are retired and their data moves into the packageThe systems of record stay, and new software connects to them
DisruptionTeams change tools together at the cutoverTeams keep their current tools until their stage arrives
Security reviewCovers the whole new platform, which is a larger reviewCovers the new software and the connections to existing systems
Cost shapeA larger program, priced as one projectA first milestone with a fixed price, then further stages
License costA per-seat or per-module subscription that grows with headcountA build cost, then hosting and upkeep, with no per-seat fee
Who changes the workflowYour administrators configure it within what the product allowsYour team asks, and it is changed in the code you own
Vendor roadmapFeatures arrive on the vendor’s schedule, with upgrades to absorbThe roadmap is yours, set by your own backlog
Data modelThe vendor’s model, mapped to your records through configurationDrawn around your records and the way you report on them
Best whenThe core systems are unsupported or cannot be changed safelyThe core systems work and the gap is in between them
How we decide

The systems map shows what each platform still does. If the gap is between systems, the first milestone fills it. If a package already fits, we say so, and if a platform has to go, that becomes a separate written scope.

Ownership

What your organization holds from the first day

Your security team can check each item below on day one. The written scope lists them, and the contract states ownership of the code.

The repository

The code lives in a GitHub organization you own. Your IT group sets who has access, and every commit is in your history.

The cloud account

Hosting, databases and keys sit in an account under your name and billing, so the runbook describes your environment and no one else’s.

Our access

We work through named accounts you create. Removing them takes one change in your directory, and the software keeps running without us.

Buyer review

Six places a security review and a rollout reach

What procurement and security teams put in front of a software supplier. Sources under each.

  1. Assurance reportAICPA

    A SOC 2 report is written by a CPA about a service organization’s controls.

    AICPA describes SOC 2 as an examination of controls relevant to security, availability, processing integrity, confidentiality or privacy. A Type 1 report speaks to controls as of a specific date. We hold no SOC 2 report, so we answer the questionnaire directly and point to your cloud provider’s own report.

  2. QuestionnairesCSA

    The Cloud Security Alliance publishes a standard set of yes-or-no security questions.

    The Consensus Assessments Initiative Questionnaire lets a buyer ask a cloud provider which security controls exist. Version 3.1 came out April 1, 2020, and the Alliance has since moved to version 4, which is the one in use for new submissions. If your team sends one, we answer it as written.

  3. Account removalIETF

    SCIM is a standard protocol for creating and removing user accounts across systems.

    Where your identity provider supports SCIM, an account removed in your directory can be removed in the software without a second step. RFC 7644 defines the HTTP-based way to manage users and groups between a directory and the applications it feeds.

  4. Audit loggingOWASP

    OWASP ranks security logging and alerting failures ninth in its 2025 list.

    OWASP notes that without logging and monitoring, attacks and breaches cannot be detected. For enterprise software that means deciding up front which actions are logged, who can read the log and how long it is kept.

  5. Secure developmentNIST

    NIST publishes a framework of secure development practices that buyers can cite.

    The Secure Software Development Framework, SP 800-218, lists high-level practices for reducing vulnerabilities in released software, in terms suppliers and buyers can share. It is guidance and not a law. We use it as the outline for the security pack, so your reviewers can read it against a document they know.

  6. AccessibilityW3C

    WCAG 2.2 is the current W3C standard for accessible web content, and tools staff use are covered by it.

    WCAG 2.2 is a W3C Recommendation, updated December 12, 2024, with three conformance levels: A, AA and AAA. Internal tools are used all day by staff, and some of them rely on keyboards or screen readers. We build to AA and name any exception in the review notes. It is a standard to build against, not a ruling on your legal duties.

What we build

Six workstreams in an enterprise build, and what each produces

Each part ends in a document or a working piece you can check against the written scope.

Interface list3 live · 2 laterERPERP (finance)SyncedAPI, read and write10:14 a.m.POST /orders503 · retried10:15 a.m.POST /orders201 · postedIdPIdentity providerSyncedDWData warehouseSynced+2CRM, warehouse managementLater

ERP and system integration

Connections to your ERP, CRM and finance tools through their APIs, with failed calls handled as set in the written scope. You receive the systems map, the interface list and a readable log for your team.

Provisioning · SCIMIn sync1PATCH /scim/v2/Users/u-28172{3"Operations": [{4"op": "replace",5"path": "active",6"value": false7}]8}204 No ContentAccess removedSign-inBlockedRoleRemoved

Single sign-on and provisioning

Sign-in through your identity provider, with accounts created and removed from your directory. You receive: the sign-in configuration and the role list, written down and tested.

Security questionnaireVersion 1Where is data stored?DiagramIn your cloud account, one regionHow do users sign in?SSO configThrough your identity providerWho can see what?Role tests14 approvers in 3 roles, testedIndependent attestationProvider’s reportNone held; provider’s report requested

Security review pack

Written answers to your security questionnaire, a data-flow diagram and a dependency scan. You receive: the answers, the diagram, the scan results and the findings with their fixes.

Data dictionaryRead-only extractapprovalsorderssitesusersrolesColumnTypeMeaningapproval_idstringPrimary keyorder_idstringERP order numbersite_idstringOne of the 6 sitesapprover_roleenumOne of 3 roles

Warehouse and reporting links

The software’s data made available to your warehouse and reporting tools in a documented shape, so analysts do not scrape screens. You receive: the data dictionary and the extract setup.

Rollout plan6 sites · 900 usersUsers0450900150450900Pilot1 site · 150Second wave2 sites · 300Third wave3 sites · 450Each stage lists a rollback step

Staged rollout

A plan that moves one site or department at a time, with a check written for each stage. You receive: the rollout plan and the rollback steps it lists.

Handover kitIn your repositoryReceiving cardOne page1Scan delivery2Match the order3Flag exceptionsAsk your site leadGuides by groupApprovers14Warehouse leads18Finance admins6IT admins4Warehouse staff858Total900

Key roles and handover

Short guides for each user group, admin notes for your IT team, and the runbook for deploys and restores. You receive: the guides, the admin notes and the runbook in your repository.

How it runs

Map, review, stage, hand over

Nothing moves to the next stage until you have signed off on the current one.

systems-map.csv

Systems map

Sample · Midwest Distribution Co. order approvals
SystemOwnerConnectionFirst milestone
ERP (finance)Finance ITAPI, read and writeYes
Identity providerSecuritySingle sign-on and SCIMYes
Data warehouseData teamRead-only extractYes
CRMSales operationsRead-onlyLater
Warehouse managementOperationsFile importLater
The two systems marked Later are named now so the design leaves room for them.

Our stack

The tools behind the build

What the systems map, the design and the code would be made with. Access goes to your IT team for the repository, the error log, the Cloudflare account and the design files. Pick a tool for the detail.

Miro
Why Miro

Miro is an online whiteboard for drawing diagrams with a group.

How we use it

We draw the systems map and data flows with your teams, so owners of each system correct it before design.

CanvasCollaborationTemplates
MiroMany
FigJamSome
MuralMany
WhimsicalSome

Questions

Enterprise software development, answered

Start here

Get your enterprise software scoped in writing

Name the system the new software has to work with first, and the review it has to pass. You’ll get a systems map, what the first milestone covers and what it costs.