Partners
Partners are the majority of our business and have had no page on this site. This is the offer, stated plainly, including the parts partners usually have to ask about.
AEC depth under your brand.
What we take on
Under your brand
- Revit, Tekla, NX and SolidWorks plugin development
- Web BIM applications on APS and ACC
- QA and release validation
- BIM production and coordination with partner-branded deliverables
Inside your process
- Your tracker, your repositories, your reporting conventions
- Your client-facing reports, written to your template
- Your release calendar, including annual Autodesk validation
At your discretion
- Named as your partner, or invisible — both are normal
- Direct participation in client calls, or never in the room
What we do not do
The first thing every partner worries about, answered before it is asked.
We do not approach your clients
Not during an engagement, not after it. No follow-up, no marketing contact, no case study naming them without your written agreement.
We do not compete for your scope
If a client of yours comes to us directly with work adjacent to yours, you hear about it from us.
We do not resell your work
Anything built under your brand is yours. IP terms are settled in writing before development, not at handover.
Start with white-label QA
The lowest-risk way to try us: a defined scope on a release you are already committed to.
Defined scope
One release, one version matrix, a fixed price and a written sign-off. No open-ended retainer to negotiate first.
Often no source access
Functional, compatibility, deployment and data-integrity testing can proceed against builds alone.
Immediate value
You get defect reports with reproduction steps and model artefacts on a release that is already in your calendar.
Platform coverage
Not a Revit shop with a side interest. These are the APIs we maintain live test environments for.
Autodesk
- Revit 2022–2027 add-ins across three .NET runtimes — 2027 moves to .NET 10 and is treated as a complexity flag in every estimate, not a footnote
- Navisworks and AutoCAD automation
- Autodesk Platform Services and ACC — Model Derivative, Design Automation, Docs and Issues
- Design Automation for Revit and AutoCAD in the cloud
Steel and structures
- Tekla Structures via the Open API — model-data extraction, detailing and numbering automation
- IFC parsing, validation and round-trip verification
- PEMB and cold-formed workflows
- Clash and coordination pipelines across federated models
Manufacturing and product design
- Siemens NX Open automation, including MBD and GD&T workflows
- SolidWorks API — server-side drawing generation, PDM integration, product configurators
- CAM and NC data preparation pipelines
- ERP and PLM connectors for engineering data
Confidentiality, IP and data
- Confidentiality
- A countersigned mutual NDA precedes any access to code, models or client data, without exception.
- Intellectual property
- Agreed in writing before development starts. Explicit in the contract rather than assumed.
- Data governance
- What leaves your environment, to which provider, with what retention — decided in week one, not at pilot review.
How an engagement starts
Feasibility Review
Thirty minutes with the engineers who would do the work, and a written verdict you can forward to your client.
Mutual NDA
Countersigned before any access. This is not a step we compress.
Scoped first phase
Fixed scope, fixed price, a working build at the end. Usually a QA engagement or a single plugin.
Standing capacity
A monthly retainer once the working relationship is proven — including annual version validation.
One partner case, correctly attributed
Quote automation with CAD generation
Delivered with Teamvoy, who led product and client communication. Consedge built the CAD generation engine and the Revit integration behind it. This case currently sits on the client-facing /projects page in a partner’s voice — moving it here is the fix.
Read the case →From prototype to production
AI made prototypes cheap. We make them ship.
A Feasibility Review is a 30-minute technical session with the engineers who would build it, followed by a written verdict: what the API actually allows, where it will break at scale, and what production costs. No obligation to proceed.
- Straight answers
- Written verdict
- Senior engineers, not account managers