Practices
Four practices, used together. An engagement begins with Operations Design inside a Wikker Blueprint; the others follow as releases are built.
Operations Design
Mapping how the work runs today, with the people who do it, and optimizing it before anything is built.
- Brought in when
- quotes depend on one person
- month-end takes a week
- nobody can say how long an order takes to fill
- What happens
- We map the process as it really runs, step by step, with the people who do it, then optimize it before anything is built.
- At the end
- a process the managers recognise, and a plan in order of value
- How long
- two to four weeks, as the Wikker Blueprint
- Who
- a senior Wikker lead, with the owner, managers and staff
- Priced
- the Blueprint fee, from C$12,000, credited against the first release
Purpose-Built Software
The applications, portals and tools that run the optimized process.
The software can include AI where it does a defined job, such as drafting documents or classifying incoming requests. A named person approves every change it proposes, and every change is logged.
- Brought in when
- off-the-shelf software never fit
- the business runs on spreadsheets and email
- a quote came back at six figures and a year
- What happens
- We build the applications, client portals, internal tools and dashboards that run the optimized process, one release at a time.
- At the end
- working software in your cloud, used by the people it was built for
- How long
- releases of two to four weeks each
- Who
- the senior lead who ran the Blueprint
- Priced
- per release, fixed before it starts, invoiced on delivery
Systems and Data
Connecting the systems a business already runs, and making its figures reliable enough to report from.
Where the data supports it, the software can include AI to classify records or forecast demand, under the same rule: a named person approves, and every change is logged.
- Brought in when
- the same record is typed into three systems
- reports are assembled by hand
- nobody trusts the figures
- What happens
- We connect the accounting, operations and customer systems already in place, and clean the data so reports can be produced from it.
- At the end
- one version of each record, and reports that run without retyping
- How long
- within releases, alongside the software
- Who
- the same senior lead
- Priced
- per release, fixed before it starts
Adoption and Care
Training, support and change once the software is in use.
- Brought in when
- new software has been bought before and nobody used it
- staff change often
- the business keeps moving
- What happens
- Training for the people who use the software, support with response times in writing, and changes as the business moves.
- At the end
- software that is used, kept running and kept current
- How long
- care plans on one- or two-year terms
- Who
- the senior lead, with the people named on your side
- Priced
- a care plan fee, set in the proposal
Technical Capabilities
The tools are chosen for the process, not the other way round. These are the capabilities an engagement draws on.
AI inside the software, where it earns its place. Drafting documents and correspondence; reading and classifying incoming requests, forms and records; extracting data from documents and PDFs; forecasting demand and workload; assistants that answer questions from the business's records. Each is built for a defined job, with a named person approving what it proposes and every change logged.
- Applications and portals
- web applications, client and supplier portals, internal tools, mobile-ready interfaces
- Workflow and automation
- approvals, scheduling and dispatch, document generation, notifications, e-signature
- Integration
- accounting, CRM, operations and productivity systems, through their published interfaces
- Data and reporting
- cleaning and joining records from many sources, reporting databases, dashboards that refresh automatically
- Maps and location data
- mapping interfaces that bring asset, network and public-record data into one view
- Cloud and security
- hosting in the client's cloud account, sign-in and access control, backups, change history and audit trails
Recent work has included mapping platforms that assemble large volumes of infrastructure and public-record data, client portals that record every release, and the automated pipelines that keep their data current.