Difficult problems.
Lightning-fast solutions.

Revenue is up. What happened to the profit?

A business can be busy, growing, and quietly destroying its own margins. The order book looks healthy. People are working hard. Yet cash remains tight and the bottom line barely moves. Cutting a few overhead expenses will not fix a business that loses money in the way it prices, sells, or delivers its work.

Lightning starts with the economics underneath the activity. Which customers and products contribute to the result? Which consume scarce capacity? Where does complexity enter the process, and who pays for it? Company-wide averages often hide the answers that matter most.

Follow the mechanism

An engagement may bring together pricing, customer profitability, workload, capacity, and working capital. These are connected decisions. A contract can look profitable on paper while tying up the people and cash needed for better opportunities.

Consider two customers with the same annual revenue. One buys a repeatable service and pays promptly. The other requires exceptions, frequent changes, and the owner's personal attention. Treating them as equally valuable can lead the company to scale precisely the wrong part of its business.

The analysis needs to distinguish allocated costs from costs that actually change with a decision. It also needs to separate accounting profit from cash timing. One spreadsheet can contain all three views, but it should not quietly substitute one for another.

Make a decision you can act on

The answer might be a pricing change, a narrower customer profile, a simpler delivery model, or a different use of capacity. It might also be a decision to stop selling something the company has offered for years. That requires more than an attractive chart. It needs a business case that survives scrutiny.

A useful model makes its assumptions visible. Management should be able to test changes in price, volume, staffing, and payment terms without rebuilding the entire analysis. Uncertainty belongs in the model rather than in a footnote nobody reads.

A good fit for Lightning

This becomes a Lightning project when the financial impact is significant and the answer crosses pricing, operations, and management information. The goal is a workable change with an observable effect, supported by a model your business can continue using after the engagement ends.

More dashboards. Still no clear answer.

A management team can have access to an enormous amount of data and still struggle to answer a basic question: what changed, why did it change, and what should we do about it? Adding another dashboard rarely fixes disagreements about what the underlying numbers mean.

Lightning begins with the decision. Who needs to make it? How often? What information would change their choice? What is the cost of being wrong or late? Those answers shape the metrics, data model, and implementation. Power BI and Excel are useful tools. They are not the reason to start a project.

Get the definitions straight

Sales, operations, and finance may use the same word for different things. Orders, invoiced revenue, recognized revenue, and collected cash each describe something useful. None is a substitute for all the others. A margin calculation also needs a clear explanation of what it includes.

When definitions are inconsistent, people spend meetings defending numbers instead of making decisions. A project can establish a shared model with traceable sources, explicit calculation rules, and clear responsibility for the inputs. The aim is to make a discrepancy understandable without reconstructing a month's worth of email.

Show what management can influence

A useful view highlights meaningful changes and their drivers. It gives the reader enough context to judge scale and urgency. It does not display every metric simply because the data happens to be available. If a number never changes a decision, it deserves less space on the screen.

Implementation may connect financial and operational systems, but the less glamorous details matter just as much: missing records, update schedules, exception handling, access rights, and maintenance. A report that requires a specialist to repair it every month has introduced a new dependency.

Adoption is part of the job

Publishing a dashboard is a technical milestone. Management using it correctly is the business outcome. The people relying on a model need to understand both its strengths and its limits. A clear handoff and an appropriate maintenance approach belong in the work from the beginning.

The finished result may be visually simple. If it answers the right question in time to act, it has done its job.

The individual systems work. The business doesn't connect.

Accounting is up to date. Invoices go out. A budget exists. Yet management still lacks a coherent view of how the business works financially. Data changes shape between systems, ownership becomes unclear at the boundaries, and cash requirements keep arriving as surprises.

Finance architecture connects the original business event to billing, accounting, forecasting, and decision-making. Software is part of that architecture. So are definitions, responsibilities, and everyday operating choices. A new platform cannot make those choices on its own.

Cash needs its own model

Profitable growth can consume cash before it generates it. Payment terms, inventory, project billing, and investment timing can matter more in the short term than a positive income statement. A forecast built by extending accounting profit may miss the actual constraint.

An engagement can bring working capital, billing practices, payments, and scenarios into one usable view. Known transactions should be distinguishable from estimates. Management needs to see where pressure may develop and which contributing factors it can influence.

A model should also support realistic updates. If maintaining it requires a complete reconstruction every month, it will stop being useful at exactly the moment the business becomes busy. The right level of detail is the level that improves decisions without creating unnecessary administration.

Fix the structure that creates the rework

When the same information is entered in several places, reconciliation can become an industry of its own. Each individual check looks reasonable. Together they may exist mainly to repair errors introduced by the process itself. That is a reason to inspect the flow from its starting point.

The work may involve reporting dimensions, accounting logic, invoicing practices, or a common structure for budgets and actuals. It also needs a clear answer to where each item of information is maintained and who owns it. Every number does not need a home in every system.

Build to the size of the business

A smaller company does not need the administrative machinery of a multinational. The objective is a structure that can support the business with a reasonable maintenance burden. Simplicity often takes more thought than adding another layer.

Lightning handles the bounded redesign. Ongoing financial administration belongs with the business's internal team or a suitable continuing partner.

Automating a bad process makes it a faster bad process.

Many workflows contain steps whose original purpose has been forgotten. They can be connected through integrations or accelerated with AI. Before doing either, it is worth asking whether the step needs to exist at all. Faster unnecessary work is still unnecessary work.

Lightning looks at the whole chain: where information originates, what happens to it, who uses it, and where people compensate for structural problems. The aim is to reduce repetitive effort and dependence on individual memory. Adding another application to the pile can easily do the opposite.

Give the technology a defined job

Repeatable work governed by clear rules differs from work requiring interpretation. The first may need a straightforward integration. The second may benefit from AI, but it requires a clear definition of the inputs, acceptable output, and handling of exceptions.

Reading a document, extracting its contents, and deciding what to do next do not necessarily belong in one undifferentiated step. A convincing demonstration can hide uncertainty about what happens when the source material is incomplete or contradictory. Those boundaries need to be explicit.

Evaluate the whole cost

The subscription price is only one part of a system's cost. Implementation, maintenance, corrections, and coordination may be more significant. The benefit should be compared with the total burden the solution creates. Sometimes a simple change in working practice removes the problem without additional software.

An implementation may combine APIs, data models, AI, and practical operating instructions. The choice follows the business requirement. A tool being technically interesting is not a customer benefit on its own.

Leave something the business can operate

A solution needs to work when its builder is no longer in the room. Access, ownership, dependencies, and failure handling therefore belong in the design. Your company should retain an understandable way of working rather than a link to a system only one outside specialist can change.

Lightning is a good fit when technology, economics, and operating practices must change together. A small isolated automation is unlikely to justify an engagement of this size. The valuable project is the one that removes a recurring constraint from the business.

If every decision needs the owner, growth has a ceiling.

What looks like a shortage of people may actually be a shortage of independent decisions. Pricing exceptions, purchasing, customer requests, and work priorities all return to the owner's desk. More employees arrive, but the owner's working day does not get shorter. There are simply more people to coordinate.

Lightning examines the business model and daily operations together. What does the company promise? Which customers are worth making that promise to? What does delivery require? Which decisions repeat, and who has enough information to make them?

Strategy needs to exclude something

When every customer, service, and exception is accepted, the calendar eventually makes the strategic choices. The company starts serving whichever demands are loudest. A useful strategy must therefore reach customer selection, pricing, and the commitments the business is willing to make.

Financial analysis helps distinguish attractive revenue from attractive business. Different options have different capital requirements, workloads, and dependencies on key people. A growth percentage alone cannot tell you what kind of company you are building.

Responsibility requires authority

Handing someone a task does not create meaningful ownership if every deviation still requires the founder's approval. The operating model needs to define what can be decided independently, on what basis, and when an issue should be escalated. People also need the information required to use that authority.

An engagement can connect responsibilities, financial measures, workflows, and systems. The point is not to produce the thickest possible manual. It is to remove recurring ambiguity that otherwise returns as another question every week.

The change should be visible in an ordinary working day

Less waiting, less duplicate work, and fewer routine approvals are more useful than a polished diagram that nobody follows. Not every judgment can be reduced to a rule, but repeated decisions can often be structured far better than they are today.

Lightning fits when commercial direction, business economics, and execution need to line up. The desired endpoint is a company that can carry on with the new approach without keeping an external adviser permanently in the loop.

When the standard answer stops being useful.

Some problems refuse to stay inside the boundaries of accounting, law, or operations. A calculation may rely on a mistaken understanding of the business. An old system may produce evidence nobody can readily use. Several individually reasonable decisions may have created an arrangement that no longer makes sense as a whole.

The first task is to establish what happened, which figures can be supported, and the precise question that needs an answer. Facts, assumptions, interpretations, and missing information should remain distinguishable. Urgency does not improve unreliable source data.

Find the break in the reasoning

An engagement may include organizing evidence, reconstructing calculations, testing interpretations, and developing a technical argument. The result needs to be traceable to the original material. Confident wording cannot compensate for weak analysis.

If the issue concerns cost allocation, for example, the underlying activity and calculation basis must be understood before the result can be assessed. The defect may lie in the evidence, the method, or how the method was applied. Those are different problems and may require different responses.

Bring in the expertise the issue requires

Lightning accepts complex assignments within its areas of competence. Where legal advice or another specialty is needed, the project can involve a trusted outside expert. An established lawyer relationship is available when the assignment calls for it.

Lightning is not presented as a law firm, and no particular authority decision is promised. The work is to create a defensible, understandable basis for moving the matter forward. That may be valuable even when the original position needs to change.

When to get in touch

The fit is strongest when the economic stakes are meaningful, the evidence is difficult, or normal progress has stalled. Explain what happened, what must now be resolved, and whether an external deadline applies. Contradictions are useful information; do not tidy them out of the initial account.

A difficult situation does not need another confident guess. It needs someone willing to establish what is supported and work through the consequences.