Skip to main content
GullySystem
Other industries

Client Portal for Photography studios

Give customers controlled access to account documents and requests.

Finance & Accounting

Does this function belong in your operation?

Use when customers repeatedly request copies, statements or account updates.

Customers need their own financial records or updates.

Online selection, editing, album design, lab printing and binding run as stages, each with an owner and a promised date, and late jobs are flagged.

Bring the records the workflow depends on.

  • Customer contacts
  • Available documents
  • Access rules

Outputs to check

  • Customer account view
  • Document-access record
  • Customer request and response history

Follow the client portal workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Authorise the contact

    Verify the person and the account they may access.

  2. 2. Prepare account data

    Choose approved documents and reconcile balances with the source.

  3. 3. Publish the view

    Expose only the permitted records and their data date.

  4. 4. Handle requests

    Route customer questions to the responsible account owner.

  5. 5. Maintain access

    Review departed contacts, document changes and resolved queries.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

The client’s accounts assistant

Downloads the bill and the statement when it suits them, even after your office has shut.

Your accounts desk

Stops attaching PDFs all morning, and sees which clients have opened their bills.

Account manager

Reads the requests raised, and answers before the client escalates to the owner.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Contact leaves the customer

Remove that person's access while retaining the business account.

Disputed invoice

Record the query without changing the issued invoice or outstanding balance automatically.

Outdated statement

Display the data date and reconcile the source before presenting it as current.

Can this work independently?

The portal needs approved customer-account data and login access. Financial documents come from invoicing or accounting, either through imports or agreed connections. Online payment and support-ticket creation are separate handoffs; customer access does not grant editing rights over the ledger.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Receipts management: Recorded customer payments and invoice allocations.
  • Ticket management: Numbered requests, ownership and resolution history.
  • Payment gateways and bank transfers: Payment references and reconciled settlement or bank evidence.

Configure, test and introduce the workflow.

  • We list the documents and actions you want to expose. You decide what stays internal. A written view of the portal pages comes back.
  • Customer records are matched to login holders. You supply contact names, and we return a trial import to check. Logo, colours and domain are applied. You get a private link to try the portal as a client would.
  • A small group goes in early. Their notes on wording and missing documents come back to you as a short list. Invitations go out in groups. Your accounts desk learns the reply screens, and phone requests for copies fall away as clients get used to the page.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Customers cannot view other accounts.
  • Balances reconcile with the ledger.
  • Requests retain submission dates.
Photography studios

How the business operates.

Wedding and portrait studios keep each booking, from advance to album delivery, in one shared record. Owners, photographers, album designers and hired cinematographers work on the same booking. It holds the date and advance, crew and call times, equipment issued, raw file handovers, the online selection, album stages and proofs, and the balance due on delivery. Each stage carries a promised date that you set.

Enquiries and packages

Record enquiries with dates, functions, budget and source, and packages with what each includes: hours, crew, spreads, prints and revisions.

Booking calendar

Show confirmed and tentative dates on one calendar, function by function, with a warning before a second booking is taken on a blocked date.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and packages. Record enquiries with dates, functions, budget and source, and packages with what each includes: hours, crew, spreads, prints and revisions.
  • Booking calendar. Show confirmed and tentative dates on one calendar, function by function, with a warning before a second booking is taken on a blocked date.
  • Advances and payment schedule. Track the advance, instalments and balance on delivery, each with a due date. Payments by cash, card, wallet or bank transfer carry a receipt number.
  • Crew assignment. Assign photographers, cinematographers, drone operators and assistants to each function with call time and venue. Double booking gets checked.

Operational bottlenecks to check

Dates can be promised twice

One booking is confirmed by call, another through social media. Both clients pay an advance. Then a crew is found at short notice.

Advances are not recorded against a name

A transfer arrives without a name against it. Months later, the client’s account of the amount cannot be checked.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry

    Record names, dates, venue, functions wanted, the package discussed and the source. A tentative hold can sit on the date. The family can decide meanwhile.

  2. 2. Date blocked against an advance

    Once the advance is received, the date is confirmed. The payment schedule goes on the booking. A second booking on a blocked date needs a deliberate override.

  3. 3. The shoot and the crew

    Assign the lead photographer, candid shooter, cinematographer, drone operator and assistants to each function with call times and venue. Camera bodies and lenses are issued against the shoot.

  4. 4. Raw files and selection

    Record the card handover, the file count and the disk it went to. A selection set goes to the client, and the chosen list returns to the studio on the booking.

  5. 5. Edit, proof and approval

    Editing and album design move through their own stages, each with a person and a promised date. Every revision is counted against what the package allowed.

  6. 6. Delivery and balance

    Record the album, prints, USB drive and gallery link as delivered on a date to a named person. Whatever is still due shows before handover.

Industry reports to connect with

  • Shoots booked by date, with the crew assigned to each
  • Advances received and balances still to collect, booking by booking
  • Jobs at each stage, from raw files through edit to album delivered
  • Albums past the date promised to the client

Questions before implementation.

When should photography studios consider client portal?

Use when customers repeatedly request copies, statements or account updates. Customers need their own financial records or updates.

What should we bring to the requirements discussion?

Bring anonymised examples of Customer contacts; Available documents; Access rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Give customers controlled access to account documents and requests. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Payments, signing and identity connections need separate scope confirmation.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Customers cannot view other accounts. Use this check when reviewing the first working version.

Talk to us

Discuss client portal for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements