Service

Small Fixes, Admin & Cleanup.

No job too small — bug fixes, content and site updates, migrations, cleanup, and the odd technical task nobody else will take on. Send us the list.

Send us the list ↓ SCOPED AFTER A FIT CALL
Intermodal port and rail systems operating as one connected network
1730 / Software Vancouver, BC · Remote
Built for

Businesses of any size with a short list of small technical jobs — and no one dependable to hand them to.

01 / Defined scope Marketing website 02 / Selected work Inspect selected work
03 / Commercial model Senior review · fixed-price gates
The problem

Built around the hard part.

  • A handful of small fixes keep getting deferred
  • You need content or site updates but your developer is gone
  • A migration, cleanup, or one-off task is stuck
  • Nobody will take on work this small
What you get

A clear path to production.

  1. 01
    Bug fixes & updates

    The small breakages and tweaks that have been sitting on the list.

  2. 02
    Content & site changes

    Copy, pages, images, and settings updated without the drama.

  3. 03
    Migrations & cleanup

    Move a site, tidy a codebase, untangle a config, close the loose ends.

  4. 04
    One-off tasks

    The odd technical job that doesn’t fit anywhere else.

Defined builds

Concrete scopes, typical timelines, and the work inside them. These are useful starting shapes, not packages we force onto your situation.

Explore all 50 build briefs →

Marketing website

A fast, static-first website for your business, built on Astro and hosted on Cloudflare.

Scope
Fit after discovery
Typical time
2–4 weeks
Open build brief →

Systems integration

Two tools that should already talk to each other, connected: CRM to accounting, accounting to spreadsheets, forms to your database.

Scope
Fit after discovery
Typical time
1–4 weeks
Open build brief →

Email automation pipeline

The transactional and notification emails your systems should be sending on their own: confirmations, reminders, status changes, renewal notices, subscriber flows.

Scope
Fit after discovery
Typical time
1–3 weeks
Open build brief →

Why 1730

Senior by default

The people in the room are the people doing the work. Direct context, fewer handoffs, better decisions.

Built to be inherited

Clear architecture, maintainable systems, and practical handover are part of the product.

Real-world first

We design around imperfect data, operational constraints, human judgment, and what must still work on Monday.

Common questions

Before we begin.

What does the engagement include?+

The exact scope is shaped around the decision or workflow that matters most. Before work starts, we set out the deliverables, ownership, decision gates, implementation path, and what is explicitly out of scope.

Who will work on the engagement?+

A senior practitioner owns the work from diagnosis through delivery and reviews every deliverable. When the scope needs additional depth, we bring in vetted specialists and remain accountable for the whole engagement. If the work genuinely needs a large on-site team, we will say so before either side commits.

How quickly can we start?+

Most focused assessments and sprints can begin within two to four weeks. The first working session confirms outcomes, constraints, stakeholders, and the smallest valuable first release.

Can 1730 work with our existing team and technology?+

Yes. We work directly with internal product, engineering, operations, and domain experts. The goal is a system your team can understand, operate, and extend — not a permanent dependency.

Do you work beyond Vancouver?+

Yes. 1730 is based in Vancouver and works with organizations across Canada and the United States. Engagements can be remote, hybrid, or include on-site discovery.

Start a conversation

Bring the messy version.

Tell us what is slow, fragmented, manual, or too risky today. We will help find the highest-leverage place to start.

One sentence is enoughCurrent state · desired outcome · timing

A senior practitioner will reply directly.