Pick a useful first step, not a mystery project.
Lightning Developments packages turn vague operational pain into buyable chunks: clarity, automation, portals, dashboards, and ongoing support.
3 paths
Clarity, build, or ongoing support
1st version
Scoped before a bigger system
NZ SMB
Designed for owner-led teams
No fog
Scope, price, and next step stated early
Main paths
Most work starts in one of these buckets.
If the scope feels obvious, choose a build path. If it still feels fuzzy, start with clarity. Very sophisticated. Almost suspiciously sensible.
Tech Clarity Session
You need a practical technology direction before buying tools or building software.
- Workflow diagnosis
- Systems roadmap
- AI readiness where relevant
- Priority actions
Automation Module
One repeated task, handover, report, or admin workflow is wasting time.
- Workflow mapping
- Build and test
- Deployment
- Handover notes
Portal / Intranet Sprint
Your team or clients need a proper place to log in, track work, and see the truth.
- Secure login
- Core records and workflows
- Roles and permissions
- Launch and walkthrough
Dashboard Sprint
The data exists, but nobody can see what changed or what needs attention.
- Metric definition
- Data connection
- Dashboard UI
- Action-focused views
Care and Improvement
You have a live system that needs sensible support, fixes, and incremental improvement.
- Bug fixes
- Small improvements
- Monitoring and advice
- Next-phase planning
Process
Scope comes before build. Revolutionary, apparently.
The point is to avoid turning a fuzzy idea into an expensive fuzzy system.
Start with the problem
Book a fit call or send the messy version. The first job is clarity.
Pick the right shape
Strategy, automation, portal, dashboard, or support. Not every problem deserves a custom app.
Scope the first version
Define what is included, what is not included, and what a useful launch looks like.
Build, launch, improve
Ship something real, check whether it works in the business, then decide the next phase.
Common add-ons
Useful extras are scoped before they become expensive surprises.
These are common extensions, not automatic upsells. If they do not solve the problem, they stay out of the quote.
Auth and access
Google or Microsoft sign-in, extra roles, two-factor authentication, and permission rules.
Data and documents
CSV imports, exports, PDF generation, document upload, validation, and structured records.
Integrations
Xero, Stripe, Google Calendar, custom REST APIs, email systems, and other business tools.
AI features
Semantic search, summaries, document processing, draft generation, and admin assistance.
What changes the price?
Users, roles, integrations, custom calculations, legacy data, approvals, and how much real-world mess has to be made usable.
What if the scope changes?
Anything outside the agreed scope becomes a written change order before work starts. No silent meter running in the background.
What should I choose first?
If you cannot describe the workflow clearly, book clarity. If you can, start a package conversation.
Next step
Still not sure which bucket fits?
Bring the rough idea, the broken workflow, or the spreadsheet that makes everyone nervous.