Skip to main content

Shan Studio

Practical AI and software for Invercargill businesses

I'm Shan, a software engineer based in Invercargill. I help Southland firms remove repetitive admin, improve internal workflows, and build the right tools properly.

You'll hear back directly from me within one business day.

Based in InvercargillWork directly with ShanFixed-scope pilotsAvailable across Southland

Services

Three ways to start, depending on how clear the problem already is

The service ladder is designed for local firms that want a bounded first step, not a vague consulting engagement.

From NZD 2,500

AI Opportunity Sprint

A structured diagnostic to find the highest-value workflow improvements before you commit to a build.

Usually 1 to 2 weeks

Small firms that know there is friction but want a clear recommendation, rough ROI, and a low-risk first step.

  • Discovery session with Shan
  • Workflow mapping and bottleneck review
  • Priority opportunities ranked by effort and payoff
  • Data and privacy considerations
  • 90-day action plan with recommended next pilot

From NZD 8,000

Workflow Pilot Build

A fixed-scope build that removes one painful manual process and proves value quickly.

Usually 3 to 6 weeks

Teams ready to fix a specific workflow such as document chasing, reporting prep, quoting admin, or internal approvals.

  • Discovery and scope confirmation
  • One production-ready workflow or internal tool
  • Integration with the systems already in use
  • Testing, documentation, and staff walkthrough
  • 30 days of post-launch support

From NZD 18,000+

Operations Copilot Platform

A broader internal platform connecting multiple workflows, dashboards, and AI-assisted operations support.

Usually 6 to 12 weeks

Growing firms that have already proven one workflow and now need a more durable operations layer.

  • Multi-workflow process design
  • Custom internal tools and role-based access
  • Reporting views and operational dashboards
  • Governance, rollout, and enablement support
  • 60 days of optimisation after launch

Who It Is For

Focused on accountants and admin-heavy Southland businesses

The strongest fit is any team losing time to repeat admin, messy handoffs, and workflows spread across too many tools.

For Accountants

Practical automation for accounting and advisory teams handling recurring reporting, follow-up, and document-heavy workflows.

  • Reduce document chasing and recurring admin
  • Keep partner review and human judgement in the loop
  • Use tools with clearer privacy and access boundaries
See details

For Southland SMEs

Workflow design and software for trades, construction, retail, and admin-heavy local operations teams.

  • Remove double-handling between inboxes, spreadsheets, and job systems
  • Speed up quoting, scheduling, and status reporting
  • Start with one fixed-scope workflow instead of a large rebuild
See details

Representative Work

Examples of the workflow problems Shan Studio is built to solve

Publishable client stories are being prepared. In the meantime, these representative pilot scopes show the kind of work that fits best.

Accounting and advisory

Recurring reporting for an accounting team

Problem

Monthly reports required too much copying between cloud tools, spreadsheets, and partner review notes.

Build

Map the reporting workflow, automate data preparation, and add review checkpoints before anything leaves the team.

Outcome

Less admin time per cycle, clearer handoff points, and faster turnaround for recurring reporting packs.

Trades and construction

Quote-to-invoice handoff for a trades business

Problem

Office staff were re-entering job details between email, spreadsheets, and invoicing tools after every quote approval.

Build

Design a fixed-scope pilot connecting quoting, approval, and job admin so the same information only gets entered once.

Outcome

Fewer manual updates, a cleaner office workflow, and better visibility on what has been approved and what still needs action.

Operations and internal admin

Status updates for a Southland operations team

Problem

Managers were chasing progress updates across email, chat, and shared files before weekly reviews.

Build

Create an internal workflow that gathers updates, summarises blockers, and puts a weekly view in one place.

Outcome

Faster weekly reviews, fewer follow-up messages, and more consistent visibility across the team.

How I Work

Direct, scoped, and built around one useful improvement at a time

The process is simple on purpose: understand the workflow, recommend the smallest valuable scope, build it properly, and stay available after launch.

01

20-minute intro

We start with a short conversation about the workflow, the systems involved, and what would make the project worth doing.

02

Discovery and recommendation

I review the process, identify the real bottlenecks, and recommend the smallest useful scope that will prove value.

03

Fixed-scope build

Once scope is agreed, I build the workflow, document it clearly, and keep communication direct and practical.

04

Support and next steps

After launch, I stay close enough to fix issues, refine the workflow, and advise on the next improvement when needed.

Privacy and Trust

Client data and access are handled with clear boundaries

This is especially important for accounting, reporting, and internal operations workflows where privacy and review discipline matter.

  • Client-approved tools only. No surprise software in the stack.
  • Access is kept to the minimum needed to complete the work.
  • Client data is not used for model training unless explicitly agreed in writing.
  • Every build includes a clear handover, support expectations, and named accountability.

FAQ

Common questions before the first conversation

The right first project should be understandable, commercially sensible, and easy to evaluate.

What does a typical first project cost?

Most first engagements start with either an AI Opportunity Sprint from NZD 2,500 or a fixed-scope Workflow Pilot Build from NZD 8,000.

Do you work with very small businesses?

Yes. The service model is designed for owner-led and small-team businesses that need one workflow improved without buying a large transformation programme.

How do you handle privacy and client access?

I keep access tight, work with approved tools, and define how data is handled before a build starts. Sensitive review points stay with your team.

How quickly can a pilot start?

If the workflow is clear and the right stakeholder is available, discovery can usually start within days and a pilot can often begin within a couple of weeks.

Bring the messy workflow, not a polished brief

If a process feels slower, messier, or more repetitive than it should be, that is enough to start the conversation.

You'll hear back directly from me within one business day.