.NET PDF Document Creator Website
Budget: $3,000 – $5,000 AUD
I need a small, secure website built on .NET where registered users can log in, choose from a set of predefined templates, and instantly generate a finished PDF. The workflow is straightforward:
• Users authenticate through a standard login screen (ASP.NET Identity is fine).
• After login they see a dashboard listing the available templates. Payment Gateway required.
• When a template is selected, questionairre is uploaded, the user completes the questionaire, the system pulls the relevant data automatically— from a SQL-based data source and from a simple form the user completes—and merges it into the template.
• The completed document is rendered as a PDF, reviewed to the admin team, once approved, then offered for download and optionally emailed to the user.
Type of users. Admin, Distributor and End User.
Distributor may introduce end users. End User who is associated to a Distributor will have dual logo on documents. Distributor also has a "reward" system based on how many End Users pay for the service. Distributor receives a monthly or quarterly report as to how many End Users have paid for the service and identifies credit which can be applied to reduce a user fee OR receives as a payment to the Distributor account.
A reminder system is created where each template has a review date. Email generated advising the document requires to be reviewed.
Key points you should be comfortable with:
• ASP.NET Core (MVC or Razor Pages) and C# for the site itself.
- Payment gateway such as stripe.
• A PDF generation library such as iTextSharp, QuestPDF, or similar.
• Clean, maintainable template handling so I can add or update templates without touching compiled code.
• Basic, responsive front-end styling; Bootstrap is fine.
• A simple admin area to manage templates, pricing and view generation logs.
Reports should be auto generated.
Acceptance criteria:
1. Authenticated users can generate at least two sample PDF templates end-to-end.
2. Templates can be updated through the admin area without redeploying code.
3. PDFs download correctly and match the filled data.
4. Source code delivered in a Git repository with build/run instructions.
If this matches your expertise, let’s discuss the technical details—data source, preferred PDF library, and deployment environment—so we can get started quickly.
Thank you.
• Users authenticate through a standard login screen (ASP.NET Identity is fine).
• After login they see a dashboard listing the available templates. Payment Gateway required.
• When a template is selected, questionairre is uploaded, the user completes the questionaire, the system pulls the relevant data automatically— from a SQL-based data source and from a simple form the user completes—and merges it into the template.
• The completed document is rendered as a PDF, reviewed to the admin team, once approved, then offered for download and optionally emailed to the user.
Type of users. Admin, Distributor and End User.
Distributor may introduce end users. End User who is associated to a Distributor will have dual logo on documents. Distributor also has a "reward" system based on how many End Users pay for the service. Distributor receives a monthly or quarterly report as to how many End Users have paid for the service and identifies credit which can be applied to reduce a user fee OR receives as a payment to the Distributor account.
A reminder system is created where each template has a review date. Email generated advising the document requires to be reviewed.
Key points you should be comfortable with:
• ASP.NET Core (MVC or Razor Pages) and C# for the site itself.
- Payment gateway such as stripe.
• A PDF generation library such as iTextSharp, QuestPDF, or similar.
• Clean, maintainable template handling so I can add or update templates without touching compiled code.
• Basic, responsive front-end styling; Bootstrap is fine.
• A simple admin area to manage templates, pricing and view generation logs.
Reports should be auto generated.
Acceptance criteria:
1. Authenticated users can generate at least two sample PDF templates end-to-end.
2. Templates can be updated through the admin area without redeploying code.
3. PDFs download correctly and match the filled data.
4. Source code delivered in a Git repository with build/run instructions.
If this matches your expertise, let’s discuss the technical details—data source, preferred PDF library, and deployment environment—so we can get started quickly.
Thank you.