Application Development Consulting: Build, Buy or Low-Code, Decided Before Anyone Writes Code

Application development consulting settles how a business app should be made before money goes into making it: bought off the shelf, built in low-code with Microsoft Power Apps, or custom-coded by developers. Lightray Solutions writes the requirements, compares the options in plain terms, and builds the Microsoft low-code solutions itself.

On Microsoft 365, the answer is often an app beside Teams, SharePoint and Outlook rather than one more system with its own login; sometimes it is a subscription, occasionally real custom code. Scoping tells you which, with the running costs written down.

The first step is a free 30-minute strategy call with Edward Pinela, MBA: send the form or phone, and he schedules it with you personally. No price is published for this work. Scoping and builds are quoted after a free strategy call, in writing, once the requirements are clear.

Should you build, buy or use low-code for a business app?

Buy when a mature product already handles the process the way your industry runs it. Use low-code when the process is specific to you and the data lives in Microsoft 365. Custom-code when the app must serve customers at scale, run complex logic or meet needs low-code cannot. The decision is about fit and running cost, not taste.

Most businesses skip this step. Someone picks the tool they know, and the mistake surfaces a year later, when the app slows down, a renewal doubles or the one person who understood it leaves. Three questions settle most cases:

• Is the process standard? Payroll, accounting and help-desk ticketing are solved problems. A subscription is usually cheaper than anything built.
• Who uses the app? Staff signed in with Microsoft 365 suit Power Apps. Thousands of public customers, or an app-store listing, point toward custom code.
• How much data, and how complex are the rules? A few thousand records and a handful of approval steps are low-code territory. Heavy calculations, very high transaction volumes or offline-first field work need a closer look.

What does scoping a business app involve?

Scoping turns an idea such as 'we need an app for inspections' into a written specification: who uses it, what each screen does, where data comes from and goes, which rules apply, and what finished means. It is the cheapest stage to change your mind, and every later quote is priced from it.

Edward runs it in a few short video sessions with the people who do the work today, not only the managers who asked for the app. The output is a document you own, whoever ends up building:

• Process map. Today's steps, handoffs and workarounds, including the spreadsheet nobody mentions until the second meeting.
• Roles and permissions. Who creates, approves, edits and only reads each kind of record.
• Data inventory. Every source the app reads or writes, such as SharePoint lists, SQL Server, Dynamics 365 or an accounting system, and who owns each one.
• First release versus later. A first version small enough to ship in weeks, with everything else on a written backlog.
• Recommendation. Build, buy or low-code, with licenses and running costs listed beside the build cost.

When are Power Apps and Dataverse the right fit?

Power Apps fits internal apps for staff who already sign in to Microsoft 365: requests, inspections, asset tracking, onboarding and case logs. Microsoft describes it as a rapid development environment for custom business apps that connect to Dataverse or to sources such as SharePoint, SQL Server and Dynamics 365, in a browser and on phones.

There are two kinds. Canvas apps start from a blank screen and suit focused tasks on a phone or tablet. Model-driven apps are generated from the data model in Dataverse, Microsoft's managed database for business apps, and suit record-heavy processes with many related tables. Dataverse adds role-based, row-level and column-level security, plus business rules that hold whichever app touches the data. Dynamics 365 keeps its data there too, so an app can work directly on your Dynamics records.

Data volume is the constraint to design around. Microsoft's delegation guidance explains that when a canvas app cannot hand a query to the data source, Power Apps works on only the first 500 records by default, adjustable to 10,000, so users can see incomplete results without realizing it. Choosing the right data source and writing delegable formulas from day one prevents that. Licensing is the other early check; the Power Platform consulting page explains it, and the approval flows around an app are covered under Power Automate consultants.

When is a custom-coded application the right call?

Custom code earns its higher cost when the app faces customers rather than staff, has to handle very large volumes or complex calculations, needs a native mobile or offline-first experience, or will be sold as a product. In those cases per-user low-code licensing and platform limits can cost more over the years than developers do.

Here is the honest division of labor. Lightray builds the Microsoft low-code side itself: Power Apps, Dataverse tables, Power Automate flows, SharePoint lists and the Power BI reporting on top. For a custom-coded application, Lightray's role is consulting, not a development team: the requirements, the specification developers quote against, help comparing their proposals, and an acceptance review of what is delivered against what was specified.

A specification that is independent of whoever writes the code protects you on price and scope, and keeps the finished app's data within reach of Microsoft 365 and your reports.

How does an application development consulting engagement run?

It runs in three stages you approve one at a time: scope, decide, then build or hand over. All of it is remote, over video calls and screen share inside your own Microsoft 365 tenant, so nothing is hosted on Lightray's systems and you own every app, table and document from the first day.

• 1. Scope. The free strategy call, then the scoping sessions and a written specification with a recommendation.
• 2. Decide. You choose build, buy or low-code with the whole cost in view: build fee, licenses and running costs.
• 3. Build or hand over. For low-code, a first release tested with real users, then documentation and training. For custom code or a purchased product, the specification and selection support go to the team or vendor you choose.

Why work with Lightray on a business app?

Because the person who scopes the app is the person who builds it. You work directly with Edward Pinela, MBA, from the first call to handover, backed by 20+ years of experience, 200+ projects delivered and a 4.9 rating on Google, with replies within 4 business hours.

Lightray also builds the reporting that business apps feed, so an inspection or request app can be designed with its Power BI dashboard in mind rather than having its data dug out later. If your sales or service teams already work in Microsoft Dynamics 365, the app can extend those records instead of copying them into a second database.

Further reading: Microsoft Learn — Understand delegation in a canvas app.