What we can build.

Concrete, named starting points. Each says who it is for, what the work involves, and a typical timeline. Commercial terms come after a short scoping diagnostic.

Browse by need

Find the closest starting point.

Search the full set by outcome, technology, or problem. Choosing a capability reveals every related option.

Representative range
Geospatial & mapping
Interactive claims and project map portal DEFINED SCOPE
Exploration and mining companies that want their land package and project story on a real map instead of a static PDF.
3–6 weeks
Drill-data dashboard DEFINED SCOPE
Exploration teams and their management who currently track drilling in scattered spreadsheets and static section images.
4–8 weeks
PostGIS migration DEFINED SCOPE
Any organization whose spatial data lives in duplicated files across shared drives, laptops, and email attachments.
2–4 weeks
Asset and infrastructure map viewer DEFINED SCOPE
Utilities, municipalities, and engineering firms whose asset data is locked in desktop GIS or CAD files that only one person can open.
3–6 weeks
Satellite and imagery change monitoring DEFINED SCOPE
Teams that need to know when something changes on the ground across areas too large or remote to visit regularly.
4–8 weeks
Site-selection and suitability model DEFINED SCOPE
Organizations choosing where to build, drill, buy, or expand, and who need to show their work rather than point at a gut feel.
4–8 weeks
Investor-facing project map DEFINED SCOPE
Companies whose website describes their projects in text while the actual locations live in a technical report nobody opens.
3–6 weeks
Land-use and consultation map viewer DEFINED SCOPE
Indigenous organizations and municipalities responding to referrals and consultations with data scattered across files and departments.
6–10 weeks
Property and parcel analysis tool DEFINED SCOPE
Developers, planners, and land teams who repeat the same multi-source parcel due diligence for every candidate property.
6–10 weeks
Route and territory optimization tool DEFINED SCOPE
Operations with field crews, deliveries, or sales territories still planned by hand on a wall map or in a spreadsheet.
6–10 weeks
Investor website with a live project map DEFINED SCOPE
Junior and mid-tier public companies whose current site is a template with a stale project JPEG.
3–6 weeks
ArcGIS app or automated workflow DEFINED SCOPE
Government, utilities, and organizations standardized on ArcGIS with under-used licenses or unscripted repetitive workflows.
2–6 weeks
Story map / scrollytelling experience DEFINED SCOPE
Companies, agencies, Indigenous organizations, and non-profits communicating something inherently spatial to communities, funders, or investors.
2–5 weeks
Data & platforms
Exploration data room DEFINED SCOPE
Companies preparing for a transaction, JV, or financing who need their project data presentable and defensible.
6–12 weeks
Sample and assay tracking database DEFINED SCOPE
Exploration teams managing hundreds or thousands of samples per season with spreadsheets and email threads to the lab.
4–8 weeks
Data monitoring and alerting job DEFINED SCOPE
Anyone who currently checks the same source manually every day or week, or finds out about changes too late.
1–3 weeks
Operational data model and reporting layer DEFINED SCOPE
Organizations where two reports of the same metric give two different numbers and nobody can say which is right.
6–12 weeks
Geochemistry and drill data cleanup and standardization DEFINED SCOPE
Exploration teams whose historical data has passed through too many hands, formats, and labs to be trusted as-is.
2–5 weeks
Internal metrics dashboard DEFINED SCOPE
Leadership teams that open every meeting debating whose spreadsheet is right instead of what to do about the numbers.
3–6 weeks
Data room for a transaction DEFINED SCOPE
Companies heading into a transaction with their documentation spread across shared drives, inboxes, and a filing cabinet.
6–12 weeks
Legacy database rescue DEFINED SCOPE
Organizations running core records on a database the original builder no longer maintains, or a spreadsheet everyone is afraid to touch.
3–6 weeks
API for your data DEFINED SCOPE
Organizations fielding recurring requests for data extracts, or whose data would be worth more if other systems could reach it directly.
2–5 weeks
AI & documents
Document extraction pipeline DEFINED SCOPE
Teams sitting on hundreds or thousands of documents whose contents need to become rows in a database, not text in a folder.
6–12 weeks
Cited document search DEFINED SCOPE
Teams that spend hours re-finding facts buried in a large document set and cannot afford answers they cannot verify.
6–10 weeks
AI meeting and report summarizer DEFINED SCOPE
Teams that record meetings or receive long reports and either write summaries by hand or, more honestly, never do.
3–6 weeks
Regulatory and registry monitor DEFINED SCOPE
Teams where someone periodically re-checks the same registries by hand, or where a missed filing has real cost.
1–3 weeks
Knowledge base with cited answers DEFINED SCOPE
Organizations whose accumulated documents hold answers that currently live only in a few senior people's memories.
4–8 weeks
Production workflow agent DEFINED SCOPE
Teams with a repeatable, high-value workflow that crosses several systems and still depends on manual copying, follow-up, or coordination.
8–14 weeks
AI evaluation and guardrail harness DEFINED SCOPE
Product and technology teams moving an AI prototype toward production, or operating a system whose quality is currently assessed by anecdote.
3–6 weeks
Websites & portals
Marketing website DEFINED SCOPE
Businesses whose current site is slow, hard to edit, or held together by a vendor they can no longer reach.
2–4 weeks
Client portal with logins DEFINED SCOPE
Firms that field the same "where is my file, what is the status" questions from clients every week.
4–8 weeks
Booking and reservation system DEFINED SCOPE
Businesses taking bookings by phone or email, or paying monthly for a booking tool that almost fits.
4–8 weeks
Member or subscription portal DEFINED SCOPE
Associations, training providers, and businesses selling access to content or tools on a recurring basis.
4–10 weeks
Online store DEFINED SCOPE
Businesses that have outgrown a template store, or whose products do not fit a standard cart at all.
4–10 weeks
Landing page system for campaigns DEFINED SCOPE
Marketing teams that lose days per campaign waiting on landing pages, or run ads pointing at slow generic pages.
2–4 weeks
Customer quote and configurator tool DEFINED SCOPE
Businesses with structured pricing whose sales team spends hours a week producing quotes that follow the same rules every time.
3–6 weeks
Apps & tools
Internal admin dashboard DEFINED SCOPE
Teams running core operations out of shared spreadsheets that keep breaking or diverging.
3–6 weeks
QGIS plugin or geoprocessing batch tool DEFINED SCOPE
GIS teams where a skilled analyst spends hours a week re-running the same multi-step process by hand.
2–5 weeks
Browser extension DEFINED SCOPE
Teams doing constant copy-paste between browser tabs because their main web tool is missing one feature.
2–4 weeks
Offline field inspection app DEFINED SCOPE
Organizations with field crews doing inspections or data collection in areas with poor or no connectivity.
6–10 weeks
Checklist and compliance app DEFINED SCOPE
Organizations that must demonstrate to a regulator, insurer, or head office that required checks were done.
4–8 weeks
MVP prototype DEFINED SCOPE
Founders and intrapreneurs who need to put a working product in front of users to test demand.
4–8 weeks
Photo and site documentation app DEFINED SCOPE
Construction, environmental, and inspection teams whose site photos are scattered across staff phones with no record of where or when.
6–10 weeks
AI review and operations console DEFINED SCOPE
Teams using AI for extraction, classification, vision, or agentic work where a human must stay accountable for exceptions and important decisions.
4–8 weeks
Automation & integrations
Systems integration DEFINED SCOPE
Businesses where someone manually copies the same records between two systems every week.
1–4 weeks
Scheduled report generator DEFINED SCOPE
Teams where a recurring report eats hours of someone's week in exports, copy-paste, and formatting.
1–3 weeks
Email automation pipeline DEFINED SCOPE
Businesses sending routine emails by hand, or losing revenue to reminders and follow-ups that never go out.
1–3 weeks
Invoice and document generation pipeline DEFINED SCOPE
Teams assembling recurring documents by hand from data that already lives in a system.
1–3 weeks
Analytics & conversion tracking setup DEFINED SCOPE
Any business running ads, SEO, or outreach that can’t currently answer "which marketing produces customers?"
1–2 weeks
Google Ads account & campaign launch DEFINED SCOPE
Businesses with high-intent, specialized services where one contract is worth far more than the ad spend to find it.
1–2 weeks
Don't see it?

If it's data, software, or a map — ask.

These are examples, not limits. Tell us what you're trying to build.

Start a conversation → See capabilities →