quintera.

Apps for your team / Priced by proposal

Give the work a shared place.

When spreadsheets and messages no longer give a clear picture, a small app may help. Start with the records, who updates them and what the team needs to decide.

Start a Power Apps project brief Explore the working example

Work directly with Felipe Quintana. Start with a brief description and a free 20-minute call to see if I can help.

The starting point

When people need different views of the same work.

  • A manager needs to see the full picture and related records. The person doing the work needs a simple update screen.
  • Work items, organizations, requests or engagements need clear relationships and consistent fields.
  • A named owner and the right IT contact can agree who uses the app, what they can access and how we will check it.

What you receive

Agree the workflow, then the app.

The proposal divides the build into clear stages. We agree which parts below your workflow needs and how much is included.

A data and workflow map

Define the records, fields, relationships, owners and status rules that support the selected workflow.

The agreed app screens

Build the screens and views needed for the named user tasks. A management app and a focused Canvas interface can serve different roles.

Checks using real tasks

Agree examples to test saving records, checking inputs, moving between screens and controlling access. Record what was tested and any limits.

A practical handover

Hand over the agreed app files and instructions, including what the app depends on and who maintains it. Clearly state what is included for moving data, rollout and support.

What is included: Request forms, approvals, tracking and dashboards are options for a project. They are not all included by default. If needed, we estimate data migration, custom connectors, integrations, licensing, rollout and ongoing support. Before work begins, the proposal confirms users, access, project stages and how we will check the result.

How we work

Start with a build we can check properly.

  1. Step 01

    Map the people and records

    Choose one workflow and identify who creates, updates and reviews each record. Confirm the environment and who approves access.

  2. Step 02

    Build the agreed first version

    Build the agreed tables and app features using approved access. Review a working example together and make the changes included in the proposal.

  3. Step 03

    Test and hand over

    Test the agreed records and user tasks, then hand over the agreed app files and instructions. Agree the next stage before adding more.

Made-up example / Not client results

Two apps. The same work-item record.

In the September 24 demonstration shown here, Quintera’s private Power Apps demonstration uses invented data: 6 companies, 12 engagements, 36 work items and 60 status updates. The management app shows related records; a focused Canvas app edits four work-item fields. A saved status change was verified after reload in both apps, then restored.

Follow the Power Apps work-tracking walkthrough

The walkthrough explains the four-table relationships, each app’s task and the fixed-date exception rules. Public resources use invented data; the browser explorer does not connect to the private apps. Ask for a guided app demonstration through the project brief.

Tested demo with made-up data
01
Beacon Harbor ServicesCompany QC002 · Approval tracker pilot QE003
02
Work item QW008Assignee, status, due date and estimated hours are editable. Record identity and engagement stay read-only.
In progressBlockedRestored
Invented records · fixed demo date September 23, 2026. Demonstration behavior, not a client case study or production guarantee.

Before we start

A few practical questions.

What has Quintera actually built for this example?

The personal demo has four Dataverse tables and two published apps using the same made-up records. Tests checked saving and reloading, seeing the saved status in both apps, Cancel, missing required fields and selected keyboard, phone and tablet behavior.

Can I open the Power Apps demonstration without signing in?

The public explorer is an illustrative website using sample data. It does not grant access to the private apps. Request a guided walkthrough through the project brief if you would like to see the actual app workflow.

Does every project need two apps or Dataverse?

No. The starting point is the workflow, approved tools and user needs. The proposal defines the data store and app approach; the two-app demo illustrates one possible design.

Can you add approvals or integrations?

We can discuss them when planning the project, after checking the tools, access and licensing needed. The current demo uses made-up data and does not include an automated approval flow, custom connector or external integration.

Are Microsoft licenses and production support included?

Do not assume they are included in the consulting fee. The proposal explains licensing, permissions, rollout and ongoing support for your organization.

Choose your next step

Start with one workflow your team needs.

Describe the records, who updates them and what a manager needs to see. That gives Felipe a starting point for the first discussion.

Start a Power Apps project brief

Prefer email? felipe@getquintera.com
No payment or commitment on this page.