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.
Enterprise software development
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 writingWhat enterprise software is
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.
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.
Your security and procurement teams get the answers in writing: where data lives, who can reach it and what is logged.
One site or department goes first, and the next group waits until you approve each stage.
Two ways in
The right one depends on what your current systems do well and how your processes differ from the package.
| Packaged softwareAdopt a vendor’s platform | Custom buildKeep the core, build what is missing | |
|---|---|---|
| Starting point | The old systems are retired and their data moves into the package | The systems of record stay, and new software connects to them |
| Disruption | Teams change tools together at the cutover | Teams keep their current tools until their stage arrives |
| Security review | Covers the whole new platform, which is a larger review | Covers the new software and the connections to existing systems |
| Cost shape | A larger program, priced as one project | A first milestone with a fixed price, then further stages |
| License cost | A per-seat or per-module subscription that grows with headcount | A build cost, then hosting and upkeep, with no per-seat fee |
| Who changes the workflow | Your administrators configure it within what the product allows | Your team asks, and it is changed in the code you own |
| Vendor roadmap | Features arrive on the vendor’s schedule, with upgrades to absorb | The roadmap is yours, set by your own backlog |
| Data model | The vendor’s model, mapped to your records through configuration | Drawn around your records and the way you report on them |
| Best when | The core systems are unsupported or cannot be changed safely | The core systems work and the gap is in between them |
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
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 code lives in a GitHub organization you own. Your IT group sets who has access, and every commit is in your history.
Hosting, databases and keys sit in an account under your name and billing, so the runbook describes your environment and no one else’s.
We work through named accounts you create. Removing them takes one change in your directory, and the software keeps running without us.
Buyer review
What procurement and security teams put in front of a software supplier. Sources under each.
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.
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.
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.
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.
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.
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
Each part ends in a document or a working piece you can check against the written scope.
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.
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.
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.
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.
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.
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
Nothing moves to the next stage until you have signed off on the current one.
Systems map
| System | Owner | Connection | First milestone |
|---|---|---|---|
| ERP (finance) | Finance IT | API, read and write | Yes |
| Identity provider | Security | Single sign-on and SCIM | Yes |
| Data warehouse | Data team | Read-only extract | Yes |
| CRM | Sales operations | Read-only | Later |
| Warehouse management | Operations | File import | Later |
Our stack
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 is an online whiteboard for drawing diagrams with a group.
We draw the systems map and data flows with your teams, so owners of each system correct it before design.
Questions
Keep exploring
Business software built around how you work, in your own repository.
Swift and SwiftUI iPhone apps, built in your own Apple Developer account.
Kotlin and Jetpack Compose apps, published from your own Google Play account.
Engineers on your product, working in your GitHub, Jira and Slack.
A remote team building in your repository, with the code in your name.
A first version at a fixed price, with a list of what to cut.
Portals, dashboards and SaaS-style tools that run in the browser.
One TypeScript codebase for iPhone and Android, in your own store and Expo accounts.
One Dart codebase for iPhone and Android, with native code where it pays.
Start here
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.